The given curl command should delete an existing client secret based on the UUID provided.
Actual Behaviour
Returns "403 Forbidden"
Reproduce Scenario (including but not limited to)
Deleting an old client secret while performing client secret rotation on a project.
Suggested Fix:
Update the curl method to DELETE on line 144 of src/pages/guides/authentication/ServerToServerAuthentication/implementation.md as below.
curl -X DELETE 'https://api.adobe.io/console/organizations/{orgId}/credentials/{credentialId}/secrets/{uuid from step 9}' \
-H 'Authorization: Bearer {ACCESS TOKEN GENERATED IN STEP 5}'
-H 'x-api-key: {CLIENT ID FROM STEP 6}'
Steps to Reproduce
Follow the steps 1-9 in src/pages/guides/authentication/ServerToServerAuthentication/implementation.md to create a client secret
On step 10, Run the below curl command provided in documentation to delete an existing client secret.
curl -X POST 'https://api.adobe.io/console/organizations/{orgId}/credentials/{credentialId}/secrets/{uuid from step 9}' \
-H 'Authorization: Bearer {ACCESS TOKEN GENERATED IN STEP 5}'
-H 'x-api-key: {CLIENT ID FROM STEP 6}'
Expected Behaviour
The given curl command should delete an existing client secret based on the UUID provided.
Actual Behaviour
Returns "403 Forbidden"
Reproduce Scenario (including but not limited to)
Deleting an old client secret while performing client secret rotation on a project.
Suggested Fix:
Update the curl method to DELETE on line 144 of src/pages/guides/authentication/ServerToServerAuthentication/implementation.md as below.
Steps to Reproduce
Platform and Version
Sample Code that illustrates the problem
Logs taken while reproducing problem