Closed
Description
openedon Aug 20, 2020
Describe the bug
When the VisualStudioCodeCredential is present, the ChainedTokenCredential throws an exception when running in production (Azure), i.e outside the local dev environment.
Expected behavior
Rather than iterate through the defined TokenCredential options, the code throws an exception as soon as it encounters the VisualStudioCodeCredentials which fails to retrieve the credential since it's not present outside the dev environment
Actual behavior (include Exception or Stack Trace)
The code throws an exception:
Error: Azure.Identity.AuthenticationFailedException: The ChainedTokenCredential failed due
to an unhandled exception: VisualStudioCodeCredential authentication failed: The operation
completed successfully.
To Reproduce
Create an application that uses Azure.Identity and Azure Blob Storage SDKs and deploy this code to Azure
- Add VisualStudioCodeCredential to the ChainedTokenCredential options
- Deploy the code to Azure WebApps
- Exception happens during authenticaiton
Environment:
- Azure.Identity 1.2.1
- Azure Web Apps running on Windows, .NET Core 3.1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Metadata
Assignees
Labels
This issue points to a problem in the data-plane of the library.Issues that are reported by GitHub users external to the Azure organization.Workflow: This issue needs attention from Azure service team or SDK teamThe issue doesn't require a change to the product in order to be resolved. Most issues start as that