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
Presently, ActiveDirectoryAuthenticationProvider implements all authentication modes but MSAL Cache location is not customizable and is in-memory by default. Cache persistence is useful for system apps that want to cache access token to file system using MSAL/Azure.Identity's cache options.
Proposed solution:
Expose API/type to enable cache persistence in OS with user options, such as:
Cache file name
Cache file location
Cache encryption (enabled/disabled)
Cache Key format
and so on..
These options can be extended based on what underlying libraries support, and most common options can be supported. Because underlying libraries are not same for all auth modes, exposing a SqlClient specific API will ensure this support continues to be available across all authentication modes that support silent authentication.
Alternatives
The only alternative solution as of now is to implement the SqlAuthenticationProvider abstract class to be able to customize cache location and enable persistence.
I still need to solidify API design proposal but putting out this feature request to exchange thoughts :)
The text was updated successfully, but these errors were encountered:
Presently, ActiveDirectoryAuthenticationProvider implements all authentication modes but MSAL Cache location is not customizable and is in-memory by default. Cache persistence is useful for system apps that want to cache access token to file system using MSAL/Azure.Identity's cache options.
Proposed solution:
Expose API/type to enable cache persistence in OS with user options, such as:
and so on..
These options can be extended based on what underlying libraries support, and most common options can be supported. Because underlying libraries are not same for all auth modes, exposing a SqlClient specific API will ensure this support continues to be available across all authentication modes that support silent authentication.
Alternatives
The only alternative solution as of now is to implement the SqlAuthenticationProvider abstract class to be able to customize cache location and enable persistence.
I still need to solidify API design proposal but putting out this feature request to exchange thoughts :)
The text was updated successfully, but these errors were encountered: