[BUG] azure-identity-extentions - WorkloadIdentityCredential with JDBC lag in response #43894
Open
3 tasks done
Labels
Azure.Identity
Client
This issue points to a problem in the data-plane of the library.
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
needs-team-attention
Workflow: This issue needs attention from Azure service team or SDK team
question
The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Describe the bug
Our application setup with Java/Maven built with docker runs on AKS alongside Azure managed PostgreSQL Flexiable server. The application connects to PostgreSQL datababase via JDBC URL which until now included the complete URL with username & password. We have now setup service connector with workload identity as describe here, which in turn allows us to pass the JDBC URL without a password relying on
AzurePostgresqlAuthenticationPlugin
/azure-identity-extentions
.Previouslly with username/password auth the query for a single row would return a response within 500 milliseconds, the same query now takes up to 30 seconds. We suspect the logs below to cause the delay in returning the expected token.
Exception or Stack Trace
To Reproduce
Code Snippet
No code changes other than passing a new format of the full connection string now including the
pluginName
.Updated complete JDBC URL
Expected behavior
The expected behavior is returning a query within 500 milliseconds, instead the query time for a single row takes up close to 30 second.
Screenshots
If applicable, add screenshots to help explain your problem.
Setup (please complete the following information):
If you suspect a dependency version mismatch (e.g. you see
NoClassDefFoundError
,NoSuchMethodError
or similar), please check out Troubleshoot dependency version conflict article first. If it doesn't provide solution for the problem, please provide:mvn dependency:tree -Dverbose
)Additional context
Add any other context about the problem here.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report
The text was updated successfully, but these errors were encountered: