SharedTokenCacheCredential must handle its cache as MSAL does because that cache is shared by applications accessing it through MSAL. The current approach, duplicating MSAL Python's logic as needed, is fragile and error prone, and adds considerable complexity. It would be better for the credential to access the cache through MSAL.
For the async SharedTokenCacheCredential, this is blocked by AzureAD/microsoft-authentication-library-for-python#88.
SharedTokenCacheCredentialmust handle its cache as MSAL does because that cache is shared by applications accessing it through MSAL. The current approach, duplicating MSAL Python's logic as needed, is fragile and error prone, and adds considerable complexity. It would be better for the credential to access the cache through MSAL.For the async
SharedTokenCacheCredential, this is blocked by AzureAD/microsoft-authentication-library-for-python#88.