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
Is your feature request related to a problem? Please describe.
As developer move from ADAL to MSAL it's important to help them with token caching.
In ASP.NET Core, Microsoft.Identity.Web provides token cache adapters/serializers but ASP.NET MVC developers are on their own.
Describe the solution you'd like
P1: Expose the token cache adapters for Memory and IDistributedCache to a new target framework (.NET 4.7.2, at least 4.6.1)
P2: Expose other classes that could be interesting, such as the certificate management, the ClaimsPrincipalExtension, and possibly the issuer validation.
Describe alternatives you've considered
Have the token cache in MSAL.NET, but currently the required target framework are not supported
Additional context
The classes in red depend on ASP.NET Core and therefore we cannot take them as is in .NET Framework. They are the classes that will require efforts if we wanted to bring them to ASP.NET developers
The classes in blue don’t have a (direct) dependency on ASP.NET Core. Unless they depend on a red class (follow the arrows), we can expose them, therefore producing value to customers, in particular:
o Support for certificates
o Possibly the issuer validation.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
As developer move from ADAL to MSAL it's important to help them with token caching.
In ASP.NET Core, Microsoft.Identity.Web provides token cache adapters/serializers but ASP.NET MVC developers are on their own.
Describe the solution you'd like
Describe alternatives you've considered
Have the token cache in MSAL.NET, but currently the required target framework are not supported
Additional context
o Support for certificates
o Possibly the issuer validation.
The text was updated successfully, but these errors were encountered: