[Feature Request] Cache MAA tokens

[gladjohn]

MSAL client type

Managed identity

Problem statement

[Feature Request] Cache MAA tokens

Proposed solution

[Feature Request] Cache MAA tokens

Alternatives

[Feature Request] Cache MAA tokens

[github-actions]

Here are some similar issues that might help you. Please check if they can solve your problem.

• [Feature Request] Redesign token caching in MSAL.NET #4257
• [Feature Request] Easier token caching #2683
• [Feature Request] In-memory shared cache cache in MSAL (like ADAL), with good performance #2849
• [Feature Request] Cache the managed identity source for an instance rather than static cache #4838

---

Possible solution (Extracted from existing issue, might be incorrect; please verify carefully)

Solution 1:

Introduce MsalAbstractTokenCacheProvider in MSAL to simplify token caching by focusing on Read / Write operations instead of the complex Before / After notifications. This can be implemented as follows:

IConfidentialClientApplication cca = ConfidentialClientApplicationBuilder
    .Create("id")
    .WithClientSecret("secret")
    .Build();

// L1TokenCache can live in MSAL
MsalAbstractTokenCacheProvider adapter = new L1TokenCache(MaxSize = "2Gb");
adapter.Init(cca.AppTokenCache);

// OR RedisTokenCacheAdapter lives in Microsoft.Identity.Web
MsalAbstractTokenCacheProvider adapter = new RedisTokenCacheAdapter();
adapter.Init(cca.AppTokenCache);

This approach can also include several out-of-the-box implementations, such as a partitioned in-memory cache for CCA, an L1 cache with eviction options, and MSAL ex cache for public clients.

Reference:

• [Feature Request] Easier token caching #2683 (comment)

Solution 2:

Provide a more general approach to token caching by allowing app developers to control how tokens are stored in memory. This can be achieved by introducing a feature like appBuilder.WithMemoryCache(MemoryCacheOptions) with options such as MaxNumberOfItems, Expiration, and Static.

MemoryCacheOptions // not all options need to be implemented at once
+ MaxNumberOfItems: int // P2
+ Expiration: DateTime // P2
+ Static : bool // P1

This approach can also include full extensibility by allowing developers to use their own implementations via appBuilder.WithMemoryCache(ITokenCacheAccessor).

Reference:

• [Feature Request] In-memory shared cache cache in MSAL (like ADAL), with good performance #2849 (comment)

Powered by issue-sentinel