-
Notifications
You must be signed in to change notification settings - Fork 344
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] [B2C] Azure AD B2C returns a 400 invalid_grant, The provided JWE is not a valid 5 segment token #2515
Comments
Upon investigation it seems when calling https://xxxxx.b2clogin.com/tfp/xxxxx.onmicrosoft.com/b2c_1_test2/oauth2/v2.0/token I tried manually posting with postman to this url with the complete code. Then I do succesfully get my token with the idp_access_token |
@bgavrilMS: to add JWE, we can just follow https://github.com/AzureAD/microsoft-identity-web/wiki/Token-Decryption
|
@samguisson we have a team with a similar issue that went through support and opened an ICM, are you from that team? |
@jennyf19 Yes, thats possible. There should be a link somewhere to this issue page in the mail. |
@samguisson thanks for confirming. I believe the B2C CxP team is working with your team now. I'll mark this as external for now, and we'll engage if we are needed. Thank you. |
Hi @samguisson
|
Version
4.28.1
Platform
.NET Framework 4.7.2
Error
Info (False) MSAL 4.28.1.0 MSAL.Desktop Microsoft Windows NT 6.2.9200.0 [03/30/2021 08:12:46 - ] Response status code does not indicate success: 400 (BadRequest).
Warning (False) MSAL 4.28.1.0 MSAL.Desktop Microsoft Windows NT 6.2.9200.0 [03/30/2021 08:12:46 - ] Request retry failed.
Info (False) MSAL 4.28.1.0 MSAL.Desktop Microsoft Windows NT 6.2.9200.0 [03/30/2021 08:12:46 - ] HttpStatusCode: 400: BadRequest
Error (False) MSAL 4.28.1.0 MSAL.Desktop Microsoft Windows NT 6.2.9200.0 [03/30/2021 08:12:46 - ] Exception type: Microsoft.Identity.Client.MsalUiRequiredException
, ErrorCode: invalid_grant
HTTP StatusCode 400
What authentication flow has the issue?
Device code flow (browserless)
Repro
Expected behavior
Should return Token with a claim that contains the token of the connected idenity provider
Actual behavior
Azure AD B2C throws a 400 Bad Request
Additional Info
We currently have 2 angular applications that succefully implement this flow without any issue.
Our WPF desktop app is the one giving the problems and we do need the Identity provider access token.
If I don't ask for this claim it works but not asking for this claim is not an option.
The text was updated successfully, but these errors were encountered: