AddDistributedTokenCaches without enabling MicrosoftIdentityWebAppAuthentication

How to make use of the distributed sqlserver cache without enabling MicrosoftIdentityWebAppAuthentication?

I have a ConfidentialClientApplication which I created using this:

public MsalAuthProvider(IMsalTokenCacheProvider tokenCacheProvider)
{
    _app = ConfidentialClientApplicationBuilder.Create("<clientid>")
            .WithClientSecret("<clientsecret>")
            .WithAuthority("<authority>")
            .WithRedirectUri("<redirecturi>")
            .Build();

    tokenCacheProvider.InitializeAsync(_app.AppTokenCache);
    tokenCacheProvider.InitializeAsync(_app.UserTokenCache);
}

In the startup you can register the IMsalTokenCacheProvider using:

services.AddMicrosoftIdentityWebAppAuthentication()
    .EnableTokenAcquisitionToCallDownstreamApi()
    .AddDistributedTokenCaches();

services.AddDistributedSqlServerCache(options => { //options... });

I want to use the sql server cache but I do not want to enable authentication towards azuread because it conflicts with my own authentication towards my own IdentityServer

services.AddAuthentication("Bearer")
    .AddJwtBearer("Bearer", options => { //options...});

Can I register / inject the IMsalTokenCacheProvider some other way so I can prevent the usage of AddMicrosoftIdentityWebAppAuthentication?

[jennyf19]

cool. we can release it after the MSAL .NET release then.

[jmprieur]

@jennyf19, @henrik-me, as discussed let’s take it in 1.3.1 (which therefore become 1.4.0) I also benefits to MSAL.NET users wanting to use net472