-
Notifications
You must be signed in to change notification settings - Fork 3k
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
ADAL to MSAL migration #18944
Comments
The rough ETA for GA is the end of October. |
@yonzhan - is this still targeted for end of oct 2021 completion? Thanks! |
@ploegert yes, it is still on track |
Overall 30% completed:We implemented cross-tenant support for MSAL integration GA and the next step is Unit Test and E2E Test based on latest MSAL 1.14.0 AzureAD/microsoft-authentication-library-for-python#400 |
Overall 60% completed: We finished testing based on latest MSAL 1.14.0 and we are working on Unit Test and E2E Test. |
Overall 75% completed: The unit tests for Azure CLI’s MSAL integration have been completed. All tests in CI show pass. Meanwhile, we need all team members to perform E2E tests on MSAL-based CLI. We will also invite other teams, like GitHub Action team, which are interested to test it too. Therefore, we plan to release a Beta version in the middle of October before the final GA release. |
Overall 90% finished. Remaining work includes:
|
We have released MSAL-based Azure CLI Beta 2.29.0.post20211020122330. You may follow https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-beta to install it, or upgrade it in the previous virtual environment:
|
Overall 95% finished, with all major tests passed. We are still testing for edge cases, like proxy, long-running operations, etc. |
Azure CLI 2.30.0 has been released which uses MSAL as the underlying authentication library. For more details, please see https://docs.microsoft.com/en-us/cli/azure/msal-based-azure-cli. |
Finally, we achieved 100% :) |
As ADAL has been deprecated:
Azure CLI needs to be migrated from ADAL to MSAL.
References
The text was updated successfully, but these errors were encountered: