Skip to content

Commit 14c3e98

Browse files
authored
Update msal-net-token-cache-serialization.md
1 parent 1de1d77 commit 14c3e98

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

articles/active-directory/develop/msal-net-token-cache-serialization.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -228,10 +228,11 @@ public static async Task<AuthenticationResult> GetTokenAsync(string clientId, X5
228228
Instead of `app.AddInMemoryTokenCache();`, you can use different caching serialization technologies. For example, you can use no-serialization, in-memory, and distributed token cache storage provided by .NET.
229229

230230
<a id="no-token-cache-serialization"></a>
231-
#### Token cache without serialization
231+
#### Token cache without serialization
232232

233-
You can specify that you don't want to have any token cache serialization and instead rely on the MSAL.NET internal cache. Use `.WithCacheOptions(CacheOptions.EnableSharedCacheOptions)` when building the application and don't add any serializer.
234-
r.
233+
Use `.WithCacheOptions(CacheOptions.EnableSharedCacheOptions)` when building the application and don't add any serializer.
234+
235+
**IMPORTANT**: there is no way to control the size of the cache with this option! If you are building a web site, web api or a multi-tenant S2S app, then use `In-memory token cache` option.
235236

236237
```CSharp
237238
// Create the confidential client application

0 commit comments

Comments
 (0)