-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] msal_extensions.token_cache.PersistedTokenCache
is bypassed by ConfidentialClientApplication
#127
Comments
@rayluo - it looks like Azure CLI has been getting quite a lot of attention on this issue, including ICMs and the scenario is very much used right now. Any objection to gettting a release out asap? |
@bgavrilMS , even if we ship this immediately, there are still some logistic steps on the Azure CLI side. After a discussion with Azure CLI team, we mutually agreed on the steps and timeline, described in the mitigation comment in the ICM. |
|
I need help to resolve this issue. |
So, you are a This issue has been fixed in msal-extensions 1.2.0b1, which is available from PyPI. This is the version that unblocked Azure CLI. Please also watch/subscribe the current repo so that you will receive notification when we ship a stable version 1.2.0 in the near future. |
Thanks for your favour. |
Describe the bug
AzureAD/microsoft-authentication-library-for-python#644 introduced a regression that
msal_extensions.token_cache.PersistedTokenCache
is bypassed byConfidentialClientApplication
.To Reproduce
Notice each time a new access token is retrieved, bypassing the token cache. Detailed analysis is provided at AzureAD/microsoft-authentication-library-for-python#644 (comment).
This causes a severe regression in OIDC authentication, so that no Azure CLI task can run longer than the OIDC token's 5-minute lifetime (Azure/azure-cli#28708 (comment)).
Expected behavior
Old access token from the token cache should be retrieved.
What you see instead
A new access token is retrieved.
The MSAL Python version you are using
1.28.0
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: