Rotate the active client secret
POST/apps-srv/apps/:clientID/secrets/rotate
An app holds at most two client secrets at a time: a retiring one and the current one. Rotation issues a new current secret and schedules the previous one to expire at previous_secret_expires_at (required, capped at 3 months from now).
Returns 409 if the app has zero secrets (use create instead), or if it already has two secrets and force is not set to true — set force to drop the oldest secret and proceed.
The plaintext client_secret is returned once in the response body.
Requires cidaas:apps_write.
Request
Responses
- 201
- 400
- 401
- 404
- 409
Secret rotated successfully
Bad Request
Unauthorized
Not Found
Conflict — no secrets to rotate, or two secrets already exist and force was not set.