-
Notifications
You must be signed in to change notification settings - Fork 867
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
[AppConfig]: Error while reading Settings from Azure App Configuration #17424
Comments
Hi @ThorstenHans, can you check if you are using valid connection string? A connection string should look this: If you have a TokenCredential, you can use |
Hey @antkmsft I double-checked the connection string. It was correct. I've also
It's keeps on throwing:
|
since filing the issue, I've updated the version of go to |
Thank you Thorsten, I was able to reproduce it - it has something to do with the region. It did not repro in West US, but does reproduce when using AppConfiguration deployed to Germany West Central. |
Thank you for finding this, @ThorstenHans! I have a fix (linked above), and there are reasons to think that Java, JS, and Python SDK may be also affected by this. .NET SDK is the only one that's ok. I will work with the other SDK teams, as well as the docs.microsoft.com team to correct code samples in this article: https://docs.microsoft.com/en-us/azure/azure-app-configuration/rest-api-authentication-hmac. It is also possible that it is actually the service that's being deployed to the German cloud is not up to the spec, and then the fix may go the other way, instead of fixing the SDK code, but I personally think it is less likely. If you have a chance to apply the fix, please give it a try! |
cool, thanks @antkmsft 🎉 |
Bug Report
Environment
What happened?
Reading settings from Azure App Configuration (AppConfig) does not work. When using a connection string for authentication, requests fail with an HTTP
401
andHMAC-SHA256 error="invalid_token", error_description="Invalid Credential"
provided as in the response header.When authenticating with
azidentity
same underlying request fail with an HTTP403
. I hadazidentity
configured to re-use existing authentication token from Azure CLI (az
).Reading the same setting works perfectly fine via
az appconfig kv show
What did you expect or want to happen?
I expect to retrieve the setting from AppConfig 😄
How can we reproduce it?
Here the fragment of the code used for authenticating with a connection string
Anything we should know about your environment.
local: I tested it on latest macOS (Intel)
cloud: see the following
az
script to spin up the required services:The text was updated successfully, but these errors were encountered: