Multiple HTTPS error and long wait time when combine MSI and local development for KeyVault access [BUG] #15626
Labels
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.
KeyVault
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
Localhost connection to Keyvault on startup will fallback multiple HTTPS requests before working and will cause long waiting time on startup. There is 1 minute delay before it start working.
Expected behavior
I would expect that the Azure Keyvault SDK does not try to get keyvault secrets without bearer.
Actual behavior (include Exception or Stack Trace)
What is the actual behavior?
To Reproduce
Here is the startup :
Environment:
The text was updated successfully, but these errors were encountered: