-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[Identity] Getting a token via VisualStudioCodeCredential using v0.10.0 of the Azure Account Extension results in an error #23249
Comments
Any workaround for bug? looks like not possible to install previous version of Azure Account. |
In the drop-down list of uninstall, there is an option "install another version". |
This issue will be addressed in a future releae. #25713 |
Hi, How do I make it work then? Has it been implemented yet? Do I still need to go back to previous version for my VSCode local app to be able to talk to Azure? Can someone point me in the right direction please? |
Hello @Jan-Kowalik-mulberryrisk! This hasn't been implemented yet. You should not roll back to a previous version of the extension as that can cause other problems. In the interim the recommendation is to authenticate using the Azure CLI. |
How do I use I tried the below but neither works:
Then I tried reverting to the old working version and it works then. |
Name of the cache where the token is stored has changed from version 0.9.11 to 0.10.0 for Azure Account extension for VS Code. As a result of this the Visual Studio Code Credential throws an error/ exception in JS with the following message because the cache with that name is not found
JS Bug filed by customer - Azure/azure-sdk-for-js#20500
VS Code Account extension bug filed by customer - microsoft/vscode-azure-account#443
The text was updated successfully, but these errors were encountered: