Rotate secret password
Endpoints
Rotate Secret Password
Syteca ACB REST API endpoint to trigger immediate password rotation on a secret — generates a new password and updates the target endpoint.
POST
Rotate secret password
Triggers immediate password rotation on the target endpoint — Syteca generates a new password matching the password policy, updates the target system, and stores the new password. Use this when you need ad-hoc rotation outside the regular schedule (responding to a possible credential compromise, end of contractor engagement, compliance audit).
For ACB deployments updated from a version prior to 1.2, switch to the
https://{hostname}/EkranACB server in the Playground.Permissions required
The user owning the Access Token must have Editor or Owner role on the secret.Synchronous trigger, async target update
The rotation is synchronous with respect to triggering, but the actual target endpoint update may take a few seconds depending on the secret type and target system response time. To check rotation status, retrieve the secret viaGET /api/secrets/{id} and inspect the password_rotation_status and last_password_rotation_utc fields (NEW in v1.4).
Errors
See Status codes. Common errors:- 403 Forbidden — user lacks Editor/Owner role.
- 404 Not Found — secret doesn’t exist.
- 500 Internal Server Error — rotation attempted but target endpoint rejected the new password. Check the Management Tool Audit Log for details. The secret’s
password_rotation_statusbecomesFailed.
Related
Heartbeat
Verify post-rotation password validity.
Update secret
Schedule rotation via the
rotation field.Get secret
Check
password_rotation_status after triggering.Data models
PasswordRotationStatus enum.