Representative route boundaries
These examples describe the application-role route gate. Passing that gate still requires resource ownership, valid inputs and the operation’s state checks. IDs below are placeholders, not authority to access another user’s work.
For an isolated acceptance check, issue a disposable application Token, use it for authenticated health and a permitted task, then verify that Token creation and approval decisions return 403. Revoke it and repeat an authenticated request; it must fail. Use a second test tenant to check foreign resource lookup/binding, separately from two application users sharing one tenant. Do not use an owner Token for those negative checks. This is a procedure, not a claim that those database-backed cases ran in this documentation update.
Issue a Token
Through Console or an owner-authorized backend:Rotate and revoke
rotate_token / rotateToken atomically revokes the old Token and returns a new ID/value with the original expiry. It does not extend lifetime. Plan the client switch because the old Token is invalid once rotation succeeds.
For application-managed overlap, create a separate Token, deploy and verify it, then revoke the old one. That is different from atomic rotation, and you own the overlap window.
revoke_token / revokeToken revokes an application Token. last_used_at helps investigate usage but does not prove every client has migrated.
If a rotation response is lost
The transaction may have revoked the old Token even though your client did not receive the replacement plaintext. Do not assume the old value remains valid or repeatedly rotate the old ID. Use an independent owner identity to inspect Token metadata and establish which IDs remain active. The lost plaintext cannot be recovered from the list: issue a separate replacement, deploy it, and revoke any unused active replacement by its ID. Record only identifiers/status in the incident log, never plaintext values. Revoking an application Token controls subsequent authentication; it is not a command to cancel an already running Run.Diagnose and verify
For 401, inspect format, expiry/revocation, and the intended control plane. A 403owner_token_required means management permission is required, not necessarily an incorrect credential.
Verify allowed execution, denied administration, rejection of the old rotated Token, preserved expiry, and failed authentication after revocation. Also verify business-user isolation and cross-tenant read/binding denial.
Sources: Tokens, authentication. Next: backend integration, security boundaries, HTTP API.