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