-
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
[BUG] ManagedIdentityCredential throws OperationCanceledException when using SqlClient #34257
Comments
//cc: @christothes |
Thank you for your feedback. Tagging and routing to the team member best able to assist. |
Hi @Rookian - Could you clarify whether or not this is occurring when you are not intending to use the I don't believe the SQLClient exposes a way to configure the options for the DefaultAzureCredential, which would allow you to set the ExcludeManagedIdentityCredential option. |
@christothes we use |
Unfortunately, your options are limited for diagnosing this since SQLClient wraps Azure.Identity in a way that does not expose the options to enable logging or configure timeouts. You may want to raise this issue there to get their take on it. |
Hi, we're sending this friendly reminder because we haven't heard back from you in 7 days. We need more information about this issue to help address it. Please be sure to give us your input. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you! |
I opened a new issue dotnet/SqlClient#1946 |
Library name and version
Azure.Identity 1.6.0, Microsoft.Data.SqlClient 4.1.0
Describe the bug
We receive almost everyday SqlExceptions with a inner OperationCanceledException.
Expected behavior
Clients might need to be able to increase the timeout or Microsoft should fix the endpoint that is responsible for providing an authentication token for
ManagedIdentityCredential
.Actual behavior
It seems like
SqlClient
tries to get a token fromManagedIdentityCredential
, but fails due to a timeout.Anything we can do here?
Reproduction Steps
Environment
Azure AppService (Linux)
.NET 6.0
The text was updated successfully, but these errors were encountered: