Open vhvb1989 opened 1 year ago
We are working to resolve this issue and will have a fix for it in next week's Identity release
Any update on this?
Having issues with this also!
@drewpayment @mitchross , have you tried identity version 1.8.2
. I was just released (4/10). It should include the fix for managed identity.
@g2vinay I would like to keep this open until this patch goes to version 1.9.0
as that's the one azd
is waiting for :)
@drewpayment @mitchross , have you tried identity version
1.8.2
. I was just released (4/10). It should include the fix for managed identity.@g2vinay I would like to keep this open until this patch goes to version
1.9.0
as that's the oneazd
is waiting for :)
1.8.2 works. I would strongly suggest unpublishing 1.8.1. This caused over a week of headaches for me.
The issue is resolved in v.1.8.2 of azure-identity..
The BOM still references 1.8.1. Please get a ticket over to the team to update BOM also.
https://central.sonatype.com/artifact/com.azure/azure-sdk-bom/1.2.11
This issue still seems to be open, when will the BOM update?
Latest BOM has the 1.8.2
version 😄 - https://central.sonatype.com/artifact/com.azure/azure-sdk-bom/1.2.12
@g2vinay I am running version 1.10.0 of Azure.Identity in a .Net 6 API and I am seeing what seems to be the exact same behavior.
I am also using 1.10 . connecting via yml configuration, works for service principle but at get following error com.azure.identity.implementation.IdentityClient.lambda$authenticateWithManagedIdentityConfidentialClient$21(IdentityClient.java:526) Microsoft.AppPlatform/Spring/logs Caused by: com.azure.identity.CredentialUnavailableException: Managed Identity authentication is not available.
azure:
keyvault:
enabled: true
endpoint: https://test.vault.azure.net/
secret:
property-sources[0]:
endpoint: "https://test.vault.azure.net/"
profile:
tenant-id: xxxxx
credential:
managed-identity-enabled: true
client-id: xxxxx
Is there any update for including the fix in 1.10 version???
I am using
build error
Caused by: com.azure.identity.CredentialUnavailableException: Managed Identity authentication is not available. at com.azure.identity.implementation.IdentityClient.lambda$authenticateWithManagedIdentityConfidentialClient$25(IdentityClient.java:563) at reactor.core.publisher.Mono.lambda$onErrorMap$28(Mono.java:3854)
Is this a known problem ?
The same it's happening to me with azure-identity version: 1.12.0
. Environment variables are defined (MSI_ENDPOINT, MSI_SECRET, AZURE_CLIENT_ID, AZURE_TENANT_ID
). The troubleshooting curl command present here returns 'Couldn't connect to server'. However, running a curl targeting the one from localhost curl -v -i "%MSI_ENDPOINT%?resource=https://myStorage.blob.core.windows.net&api-version=2019-08-01" -H "X-IDENTITY-HEADER: %IDENTITY_HEADER%"
does return a token. One of the things I did not try is to regenerate the 'system assigned identity', but this could be risky as it could break other things.
When using identity version: 1.8.1 https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/identity/azure-identity/CHANGELOG.md#181-2023-03-06, my application running on App-services can't use the
DefaultAzureCredential
to authenticate with Manage Identity.Error:
Switching back to version
1.8.0
(and below): https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/identity/azure-identity/CHANGELOG.md#180-2023-02-03 fixes the issue and the app works as expected.My app is using Java-spring auto-config to pull secrets from key vault as application settings with:
My POM:
Source code: https://github.com/Azure-Samples/todo-java-mongo/tree/staging/src/api