Rotate a federation enrollment

Changed on

Transactionally revokes active project-scoped grants for the spoke and installs the caller-supplied replacement token. Database account tokens cannot rotate legacy grants; use relay enrollment credentials so issuer expiry and revocation remain enforced. In identity mode, bootstrap credentials require actor to name an existing hub account with an unscoped API token, including expired or revoked tokens. The actor must be able to see a project-scoped grant's project. Direct grants remain valid after account tokens expire or are revoked. After canonical capability normalization and actor resolution, an exact replay with the same replacement token, spoke instance, project, canonical capabilities, resolved actor, and adoption policy returns the same active enrollment. An attribute mismatch or revoked replacement enrollment returns 409 with code federation_enrollment_token_conflict.

post/api/v1/federation/enrollments/actions/rotate

Request

  • The document declares no server URL.
  • Auth
    none declared

Request body

actorstring
allow_adoption_snapshot_authorsboolean
capabilitiesstring required
project_idinteger required
spoke_instance_uidstring required
tokenstring required

Response

OK

actorstring required
capabilitiesstring required
created_atstring date-time required
idinteger required
project_idinteger nullable required
revoked_atstring date-time
spoke_instance_uidstring required
tokenstring
updated_atstring date-time required

Changes