Token Vault is currently available in Early Access for public cloud tenants. To enable Token Vault, contact your Auth0 representative.
- Microsoft
- Box
- Slack
- GitHub
- Connect
- Custom social connection
How it works
When a user authenticates with a supported external provider and authorizes the federated connection:- Auth0 obtains access tokens using OAuth 2.0 scopes to control access. Users explicitly approve requested permissions.
- Auth0 securely stores federated access and refresh tokens in the Token Vault.
- The application links user accounts with the user’s consent. As a result, the user won’t have to create separate accounts for each external provider.
- Your application calls Auth0 to exchange a valid Auth0 refresh token with an access token for a federated connection. Your application can perform this exchange multiple times while Auth0 manages refreshing the federated access tokens stored in the Token Vault. Using a federated access token, your application can call third-party APIs on the user’s behalf.
Common use cases
Learn about some common Token Vault use cases:- A user downloads a productivity app that integrates with Auth0 and connects their Google and Microsoft user accounts. With user account linking, they can log into the productivity app using a single set of credentials managed by Auth0.
- An AI agent integrated into an application calls third-party APIs to perform tasks on the user’s behalf, such as scheduling a meeting in Google Calendar.
Get started
To get started with Token Vault, read the following:Read… | To learn… |
---|---|
Configure Token Vault | How to configure the Token Vault. |
Call APIs with Token Vault | How an application accesses the Token Vault to get an access token to call third-party APIs. |