Skip to content

Commit 56125be

Browse files
Update articles/container-apps/token-store.md
Co-authored-by: Anthony Chu <[email protected]>
1 parent 41503ab commit 56125be

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

articles/container-apps/token-store.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,13 +11,16 @@ ms.author: cshoe
1111

1212
# Enable a token store in Azure Container Apps
1313

14-
Token stores are a repository for security tokens associated with your container app. When you use a store, your app is better able to achieve:
14+
Azure Container Apps authentication supports a feature called token store. A token store is a repository of tokens that are associated with the users of your web apps and APIs. You enable a token store by configuring your container app with an Azure Storage account.
1515

16-
- **Portability**: With authentication details stored independently of your application, you can easily switch the user security context as you move from development, to staging, to production.
16+
Your application code sometimes needs to access data from these providers on the user's behalf, such as:
1717

18-
- **Fault tolerance**: With your authentication data isolated from each container, your security profile is stable even if your container experiences problems.
18+
* post to the authenticated user's Facebook timeline
19+
* read the user's corporate data using the Microsoft Graph API
1920

20-
- **Centralized security**: With your security stored together, you can maintain your app's security tokens in a single place.
21+
You typically must write code to collect, store, and refresh these tokens in your application. With the token store, you just [retrieve the tokens](https://learn.microsoft.com/en-us/azure/app-service/configure-authentication-oauth-tokens#retrieve-tokens-in-app-code) when you need them and [tell Container Apps to refresh them](https://learn.microsoft.com/en-us/azure/app-service/configure-authentication-oauth-tokens#refresh-auth-tokens) when they become invalid.
22+
23+
The ID tokens, access tokens, and refresh tokens are cached for the authenticated session, and they're accessible only by the associated user.
2124

2225
## Generate a SAS URL
2326

0 commit comments

Comments
 (0)