Getting a token via VisualStudioCodeCredential using v0.10.0 of the Azure Account Extension results in an error

[wwlorey]

• Package Name: @azure/identity
• Package Version: latest
• Operating system: Windows
• nodejs
  • version: 17.5.0
• browser
  • name/version: N/A
• typescript
  • version: 4.0.2
• Is the bug related to documentation in
  • README.md
  • source code documentation
  • SDK API docs on https://docs.microsoft.com

Describe the bug
In version 0.10.0, the Azure Account Extension for VS Code started consuming the VS Code secrets API instead of using keytar directly for caching tokens. It looks like the identity package relies on the old way the extension was using to store these tokens as demonstrated by the following error. This is sometimes thrown when users attempt to get tokens using VisualStudioCodeCredential:

To Reproduce
Please see the repro steps in microsoft/vscode-azure-account#443 (comment) and more info in microsoft/vscode-azure-account#443 (comment).

Expected behavior
The identity package succeeds in reading tokens cached by the Azure Account Extension.

More info
A more robust way of talking to the Azure Account Extension is through the extension API if that's an option for this package.

[KarishmaGhiya]

Thank you for filing the bug. The change in the cache name to store token has affected identity libraries in all languages. We are working on a solution. We will have an update for you before next Wednesday

[KarishmaGhiya]

@wwlorey I have a question for the VS Code team here - microsoft/vscode-azure-account#443 (comment)

[StephenWeatherford]

@wwlorey Does this affect all extensions that use azure account, or are we (the Bicep extension with some new code) affected by this based on us doing something differently? Don't fully understand why you don't publish a reverted version to fix this until you get a real fix, especially if it's not just us. Thx.

cc @ucheNkadiCode, @bhsubra

[billwert]

This issue has been mitigated for Copper and will be resolved more fully in Zinc. #22904