-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Error logs cluttered with instances CredentialUnavailableException #19213
Comments
Thank you for your feedback. Tagging and routing to the team best able to assist. |
This is the logging to diagnose which chained credentials failed for |
@rodgersmith Thanks for filing this issue and reaching out for more information. As @heaths mentioned the behavior of credentials in the However, if you receive the top level error you stated above:
This would indicate that none of the attempted credentials were able to retrieve a token and the authentication failed. In this case the initial call to |
Hi @schaabs. I have implemented the DefaultAzureCredentialOptions in order to exclude the unnecessary credential types. The relevant failure we encounter is :
This issue happens intermittently with no good way of predicting it. 9 times out of 10 it connects correctly. We are connecting to an Azure db via EntityFramework 5.02 Azure.Identity: 1.3. The environment is an AKS cluster. |
We changed the code a bit to stop using the DefaultAzureCredential entirely and the issue is gone now. |
machinelearningservice-typescript.md-update (Azure#19213)
Describe the bug
Please provide the description of issue you're seeing.
We recently implemented authenticating with Azure Key vault using Managed Service Identity. It seems that for the majority of the time we are authenticating as we expect to, but our error logs are overloaded with errors detailing the instances where this failed. On a typical day we see hundreds of the same typical exception. Is this expected behavior or are we doing something wrong?
Azure.Identity.CredentialUnavailableException: DefaultAzureCredential failed to retrieve a token from the included credentials.
``
Environment:
Our Startup.cs fetches the keyVault configs we will need:
And the dbContext where we fetch the token to connect to the db.
(note: we have several different schemas we connect to per dbContext so we do not wire this up in the startup)
The text was updated successfully, but these errors were encountered: