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
[Bug] Using the SHA2 feature will cause the following errors #4690
Comments
Very strange, as we have integration tests that check this flow. We use pfx based certs. Need to test |
@neha-bhargava - can you please take a look at this one. |
I just tried a PEM cert and received a token using the latest package. Can you share how you are creating the PEM certificate? Maybe this is an edge case. |
From a preliminary investigation from a partner team this looks like an external issue (AAD) that is affecting MSAL 4.60.0, I will keep you updated here when the issue has been fixed. Please rollback to a previous version of MSAL until then |
As the bug report indicates, targeting version 4.59.0 of the MSAL assemblies is a sufficient workaround to this issue for now. Note that the "library version used" in the bug has a typo, and this issue applies to 4.60.0 specifically. |
Working on releasing MSAL 4.60.1 to NuGet, will update here after the release. |
Library version used
4.46.0
.NET version
Any
Scenario
PublicClient - desktop app
Is this a new or an existing app?
None
Issue description and reproduction steps
When getting a token by certificate
Microsoft.Identity.Client.MsalServiceException: AADSTS5002730: Invalid JWT token. Unsupported key for the signing algorithm. Trace ID: c985e53a-e233-4b56-88f0-bfcd91e20c00 Correlation ID: ef66443e-1b8d-43f8-9d6e-af2a090818ee Timestamp: 2024-03-29 01:38:20Z
Relevant code snippets
Expected behavior
No response
Identity provider
Microsoft Entra ID (Work and School accounts and Personal Microsoft accounts)
Regression
No response
Solution and workarounds
Downgrade MSAL to version 4.59.0
The text was updated successfully, but these errors were encountered: