You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like you already today provide the customer the option to register the caches to service collection. You are also creating a separate caching package without the ITokenAcquisition API.
The user might take advantage of the native pattern of registrations the cache implementation to DI. But then the actual cca/cache glue code is provided only within the TokenAcquistion APIs [1,2] not on CCA extension methods.
Could you maybe add an extension to IConfidentialClientApplication method that expects IServiceProvider and another one that directly expects IMsalTokenCacheProvider so that customers can
continue with their DI pattern on app initialization.
not need to know about the specifics of cache integration pattern between CCA and Id.Web
The text was updated successfully, but these errors were encountered:
@jmprieur the current API re-initialize the ServiceCollection from scratch. My proposal is that the user has already registered the Microsoft.Extensions.* caches into his DI (ServiceProvider) already at app startup. IMHO Id.Web should provide a way to work with such ServiceProvider as well. Not just this from-scratch way.
The missing signature I had in mind is: public static IConfidentialClientApplication AddInMemoryTokenCache( this IConfidentialClientApplication confidentialClientApp, IServiceProvider serviceProvider)
It seems like you already today provide the customer the option to register the caches to service collection. You are also creating a separate caching package without the ITokenAcquisition API.
The user might take advantage of the native pattern of registrations the cache implementation to DI. But then the actual cca/cache glue code is provided only within the TokenAcquistion APIs [1,2] not on CCA extension methods.
Could you maybe add an extension to IConfidentialClientApplication method that expects IServiceProvider and another one that directly expects IMsalTokenCacheProvider so that customers can
The text was updated successfully, but these errors were encountered: