Update RBAC Client
Edit a client's profile or rotate credentials. Profile fields (identifier, display_name, email, metadata, status) are written from the request on every call, so omitting one sends an empty value and clears it — send the full desired state. Credential fields (username, password, token) are only touched when non-empty, so omitting them leaves the existing credential intact.
To rotate credentials: pass a new password and/or token — the old hashes are replaced. Pass auto_generate_token: true to mint a fresh token; the new value comes back in generated_token (only once). Role/membership changes are not handled here — use /rbac/memberships. Any identities in the body are ignored on update.
Changing status here is OK but PUT .../status is the dedicated route used by the dashboard's disable/reactivate button.
Path parameters
Request body
Same field set as create (strict decoding — unknown fields are rejected), except identities is ignored and there is no role_ids:
invited | active | disabled | revoked (empty defaults to active). Prefer the dedicated status endpoint when only changing status.Response (200 OK)
Updated client (same shape as list entries), plus generated_token if a fresh token was minted.
Errors
identifier, invalid status, or attempt to use a disabled credential method.endpoints:update permission in the active account.