Virtual Account tokens
Virtual Accounts are the API keys your applications use. Rotation is zero-downtime: the new token is issued immediately, and the old one stays valid for a grace period you choose. For scheduled rotation, notifications, and syncing tokens to a secret store, see Manage Virtual Accounts.Open the Virtual Accounts list

Virtual Accounts list
Open the account's tokens and regenerate

Manage tokens dialog
Choose the grace period
- A new token is created immediately.
- The old token keeps working for the full grace period.
- When the grace period expires, the old token is invalidated.
Swap it in and verify
Personal Access Tokens
PATs are per-user credentials.For individual users
Revocation is immediate — every existing PAT stops working the moment the admin clicks Revoke all PAT. Each user then generates a new token under Access → Personal Access Tokens and uses that one from then on. To revoke PATs for a single user instead of the whole tenant, use Revoke All PATs on that user from Access → Users. See User management.For scripts, CLI sessions, and integrations
Any script, CLI session, or integration authenticating with a PAT will fail until its token is updated. Plan this outside business hours as much as possible.Open Revoke all PAT
Revoke every PAT

Revoke all PAT in Account Management
Issue new tokens
MCP Server credentials
MCP server credentials have no grace period, so rotation is a three-step process: create the new credential at your provider, update it in TrueFoundry, then invalidate the old one. For auth architecture and revoking every stored token on a server at once, see MCP Gateway authentication and security.Generate a new credential at your provider
Update the credential in TrueFoundry
- API Key
- OAuth2
Authorization header). The header name stays the same; only the value changes.
API Key auth with a shared header value
Bearer {{API_KEY}} and each user updates their own key instead — no change is needed here. See Auth Overrides.Invalidate the old credential at your provider
Gateway installation tokens
The gateway installation token (GatewayToken) is how a self-hosted AI Gateway authenticates to the TrueFoundry control plane. Tokens are bound to a gateway installation entry — there is no regenerate action — so rotation means creating a new installation, cutting the running gateway over to its token, deleting the old installation, and restoring the real URL on the new one.
You create the new entry with a temporary example URL because the real gateway URL is still attached to the old installation. After the old entry is deleted, you edit the new entry and set the real URL.
For the create and token APIs used at first install, see Deploy Gateway Plane.
Note the current installation
https://gateway.example.com). You need the URL again when you fix the new entry at the end.Create a new gateway installation with an example URL
https://gateway-rotate-temp.example.com — so the create succeeds while the real URL still belongs to the old installation.
Create Gateway Endpoint
Generate the new GatewayToken and cut over the running gateway
GatewayToken, store it securely, then update the Kubernetes secret the gateway reads (typically TFY_API_KEY on truefoundry-creds) and restart the gateway so it authenticates with the new token. Confirm the gateway is healthy against the control plane before continuing.Delete the old gateway installation
Fix the URL on the new installation
https://gateway.example.com). Save, then confirm clients still reach the gateway at that URL and that the gateway remains connected to the control plane.Via the API, send the full manifest including isDefault:SCIM tokens
The SCIM bearer token is what your identity provider uses to call TrueFoundry’s SCIM API for user and team provisioning. Rotation issues a new token immediately; the previous token stays valid until its expiry period ends, so you can update the IdP before provisioning breaks. For first-time SCIM setup, see SCIM provisioning and the IdP-specific guides under SSO.Open SCIM configuration

SCIM on the Provisioning page
Regenerate the token

SCIM configuration with Regenerate token
Update the bearer token in your IdP
