-
Notifications
You must be signed in to change notification settings - Fork 3.3k
{Core} Bump MSAL to 1.27.0 and pin pymsalruntime to 0.14.0
#28556
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
Conversation
️✔️AzureCLI-FullTest
|
️✔️AzureCLI-BreakingChangeTest
|
|
Core |
| pycparser==2.19 | ||
| PyGithub==1.55 | ||
| PyJWT==2.4.0 | ||
| pymsalruntime==0.14.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
MSAL 1.26.0 requires
pymsalruntime>=0.13.2,<0.14; python_version>='3.6' and platform_system=='Windows'
So the latest allowed pymsalruntime is 0.13.12.
MSAL 1.27.0 requires
pymsalruntime>=0.13.2,<0.15; python_version>='3.6' and platform_system=='Windows'
If pymsalruntime 0.13.12 is already installed, azdev setup -c won't upgrade it to 0.14.0, so pymsalruntime is explicitly bumped and pinned to 0.14.0.
Meanwhile, as Azure CLI doesn't directly depend on pymsalruntime, pymsalruntime is not pinned in setup.py and any version allowed by MSAL is acceptable.
Related command
az loginDescription
MSAL 1.27.0 (AzureAD/microsoft-authentication-library-for-python#669) contains several improvements.
The most significant one is to tolerate ID token time errors (AzureAD/microsoft-authentication-library-for-python#657) which will solve 2 very common issues:
az login: RuntimeError: 0. The ID token is not yet valid. #20388)az loginfails: RuntimeError: 9. The ID token already expires. #23223)pymsalruntime0.14.0 started to support Python 3.12: https://pypi.org/project/pymsalruntime/0.14.0/#files