[Feature Request] In memory token cache in confidential client application is well partitioned for all flows, non longer serialized and can be shared between instances of confidential client apps

Is your feature request related to a problem? Please describe. For context see Token cache vision 1-pager

Describe the solution you’d like Out of the box, confidential client applications should internally have a token cache which is:

• well partitioned for all flows. (Today, this is the case for AcquireTokenForClient only)
• no longer using serialization when an external token cache serializer is not hooked-up (like the work done on https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/issues/2826)
• P1: It should be possible to ensure that this token cache is shared between instances of confidential client applications, as was the case with ADAL. See https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/issues/2849#issuecomment-908316278
• P2: It should be possible to provide eviction parameters. See https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/issues/2849#issuecomment-908316278

P1:

ConfidentialClientApplicationBuilder.Create(clientId)
                                                          .WithDefaultCache(shared: true) // Shares the cache between instances of CCA

P2:

ConfidentialClientApplicationBuilder.Create(clientId)
                                                          .WithDefaultCache(shared: false,
                                                           new EvictionParameters(sizeSimit:1000,
                                                                                                  slidingExpiration: TimeSpan.FromMinutes(30) )
                                                          );

Describe alternatives you’ve considered see Token cache vision 1-pager

Additional context This issue overrides:

[jmprieur]

@zhenyar. I think that this was defensive code due to the fact that ADAL’s cache had not initially been designed to support some scenarios. You shouldn’t need to do any of that with MSAL. I would recommend you just delete this code.

[zhenyar]

When is the default cache support expected to be available in Microsoft.Identity.Client? Will the default cache support multi-tenant OBO, username/password and client credentials auth flows?

Unfortunately Microsoft.Identity.Web.TokenCache is not going to work for me due to nuget hell.