Closed sam-piper-lendus closed 3 weeks ago
@sam-piper-lendus please revert to use v1.12.x of Azure.Identity until we can identify the issue.
cc: @christothes how does Azure SDK determine if the source is GitHub in Managed Identity flows? or were you using the two legged CCA flow here before? to exchange GitHub assertion for a AAD token?
I believe this bug is resolved by the following PR which has not yet shipped in a patch - https://github.com/Azure/azure-sdk-for-net/pull/46711.
Thanks @christothes
@sam-piper-lendus marking as external as this fix was made by Azure SDK - https://github.com/Azure/azure-sdk-for-net/pull/46711.
+1 we are also seeing this in 13. rolling back to 12 has fixed for now.
@aherrick - thanks for reporting. This will be fixed in Azure SDK 1.13.1 or 1.40.0 (whichever comes first).
Library version used
4.65.0
.NET version
.NET 8
Scenario
ManagedIdentityClient - managed identity
Is this a new or an existing app?
The app is in production, I haven't upgraded MSAL, but started seeing this issue
Issue description and reproduction steps
I know there is an existing issue open for this, but we are getting the same problem with a different stack trace, so wanted to make sure our issue scenario was provided as well.
Our GitHub Actions workflow for main CI build is failing after upgrading to v1.13 of Azure.Identity, which uses MSAL 4.65 I believe for token acquisition now. The failure is coming from trying to load KeyVault secrets, works fine on v1.12.x of Azure.Identity.
The stack trace we are getting below is generated when we try to run Swashbuckle CLI on our API projects to generate swagger.json files:
Relevant code snippets
No response
Expected behavior
No response
Identity provider
Microsoft Entra ID (Work and School accounts and Personal Microsoft accounts)
Regression
No response
Solution and workarounds
No response