Cancel Secret Rotation
POST
clients/{id}/secret:cancel
Cancel the secret rotation. This will discard the prepared secret.
If there is no prepared client secret ready, an attempt to cancel will fail with a 409 status.
Resource Information
| Method and URI | POST https://developer.api.autodesk.com/applications/v2/clients/{id}/secret:cancel |
| Authentication Context | App only |
| Required OAuth Scopes | application:client:rotate_secret |
| Data Format | JSON |
Request
Headers
| Authorization* string | Must be Bearer <token>, where <token> is a two-legged access token obtained via a Client Credentials Grant flow. |
| Content-Type* string | Must be application/json |
* Required
Request
URI Parameters
| id string | The client ID of the application to cancel secret rotation. |
Request
Body Structure
| clientAssertion* string | A JWT signed by the application. The assertion must be signed by one of the keys published at the application’s JWKS URI. The supported signature algorithms are ES256, ES384, ES512, PS256, PS384, and PS512. The JWKS URI can be configured on https://aps.autodesk.com/myapps.
The JWT must contain the following claims:
|
* Required
Response
HTTP Status Code Summary
| 200 OK | Successfully cancelled the prepared client secret. |
| 400 Bad Request | Malformed request. The request body is not valid. See response for details. |
| 401 Unauthorized | The request did not have a valid access token. Obtain a fresh access token and try again. |
| 403 Forbidden | You do not have permission to perform the operation specified by the request. |
| 404 Not Found | Not Found |
| 409 Conflict | No prepared client secret to cancel. |
Example
Successfully cancelled the prepared client secret.
Request
curl -v 'https://developer.api.autodesk.com/applications/v2/clients/:id/secret:cancel' \
-X 'POST' \
-H 'Authorization: Bearer AuIPTf4KYLTYGVnOHQ0cuolwCW2a' \
-H 'Content-Type: application/json' \
-d '{
"clientAssertion": "eyJ..."
}'
Response
{}