Skip to content
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

Closed
KarishmaGhiya opened this issue Mar 1, 2022 · 6 comments
Assignees
Labels
Azure.Identity blocking-release Blocks release bug This issue requires a change to an existing behavior in the product in order to be resolved. Client This issue points to a problem in the data-plane of the library.
Milestone

Comments

@KarishmaGhiya
Copy link
Member

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
image

JS Bug filed by customer - Azure/azure-sdk-for-js#20500
VS Code Account extension bug filed by customer - microsoft/vscode-azure-account#443

@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Mar 1, 2022
@azure-sdk azure-sdk added Azure.Identity Client This issue points to a problem in the data-plane of the library. needs-team-triage Workflow: This issue needs the team to triage. labels Mar 1, 2022
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Mar 1, 2022
@KarishmaGhiya KarishmaGhiya assigned xiangyan99 and chlowell and unassigned g2vinay Mar 1, 2022
@KarishmaGhiya KarishmaGhiya added this to the [2022] April milestone Mar 1, 2022
@KarishmaGhiya KarishmaGhiya added bug This issue requires a change to an existing behavior in the product in order to be resolved. blocking-release Blocks release labels Mar 1, 2022
@KarishmaGhiya KarishmaGhiya changed the title [Identity] Cache name change for secrets causes exceptions thrown for Visual Studio Code Credential [Identity] Getting a token via VisualStudioCodeCredential using v0.10.0 of the Azure Account Extension results in an error Mar 1, 2022
@xiangyan99 xiangyan99 removed the needs-team-triage Workflow: This issue needs the team to triage. label Mar 17, 2022
@joshfree joshfree modified the milestones: [2022] April, [2022] June Mar 26, 2022
@scottaddie scottaddie pinned this issue Mar 28, 2022
@jsquire jsquire unpinned this issue Mar 31, 2022
@joshfree joshfree modified the milestones: [2022] June, [2022] July Jun 6, 2022
@joshfree joshfree modified the milestones: 2022-07, 2022-08 Jul 5, 2022
@lidong-zhao
Copy link

Any workaround for bug? looks like not possible to install previous version of Azure Account.

@xiangyan99
Copy link
Member

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".

@chlowell chlowell removed their assignment Aug 1, 2022
@billwert
Copy link
Contributor

This issue will be addressed in a future releae. #25713

@Jan-Kowalik-mulberryrisk

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?

@billwert
Copy link
Contributor

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.

@Jan-Kowalik-mulberryrisk

How do I use az login in combination with launch.json config? VSCode starts apps, that are configured with it, in a new terminal/shell.

I tried the below but neither works:

  • running az login in a terminal and then running the app with F5
  • running the app with F5; killing it; running az login in the app terminal and starting the app again with F5

Then I tried reverting to the old working version and it works then.

@github-actions github-actions bot locked and limited conversation to collaborators May 15, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Azure.Identity blocking-release Blocks release bug This issue requires a change to an existing behavior in the product in order to be resolved. Client This issue points to a problem in the data-plane of the library.
Projects
Development

No branches or pull requests

9 participants