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 #27263

Closed
KarishmaGhiya opened this issue Mar 1, 2022 · 3 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

KarishmaGhiya commented Mar 1, 2022

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

@KarishmaGhiya KarishmaGhiya added Client This issue points to a problem in the data-plane of the library. Azure.Identity 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 added this to the [2022] April milestone 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
@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 29, 2022
@joshfree joshfree modified the milestones: [2022] June, [2022] July Jun 6, 2022
@ucheNkadiCode
Copy link

@joshfree, what's the update on this? Has work begun so far?

@bhsubra
Copy link

bhsubra commented Oct 27, 2022

Is there any update on this issue?

cc: puicchan

@KarishmaGhiya
Copy link
Member Author

KarishmaGhiya commented Dec 7, 2022

Hello, the next steps for this issue are tracked here - #30525
This work is planned for the first half of next year. In the interim we recommend the workaround suggested in the troubleshooting guide of using the Azure CLI. (cc: @billwert )

schaabs pushed a commit that referenced this issue Aug 11, 2023
Issue #27263 has been closed, supersceeded by #30525.
A user could read #27263 begin closed as meaning the known issue is resolved.
Pointing the link directly to the current issue to avoid any confusion.
@github-actions github-actions bot locked and limited conversation to collaborators Oct 19, 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

7 participants