Got Invalid_client error using Azure B2C as Identity Provider in the OpenId SSO | Community
Skip to main content

Got Invalid_client error using Azure B2C as Identity Provider in the OpenId SSO

  • April 9, 2024
  • 5 replies
  • 0 views

Hi,

 

We have follow the instruction to configure SSO based in OpenID with our Azure B2C Identity Provider but got a invalid_client error after successfully authenticated our user.

What are we missing in the configuration of this solution ?

 

Kind regards

 

5 replies

Caroline13

Hey Guillaume, can you share a bit more about how you've set up the OIDC configuration form and where you're getting this error?


Hi,
Our setup seems for us quite common for an OpenID integration :


 


Caroline13

We've checked on our side and we're seeing some errors, but none of them specific to an “invalid_client” error interestingly enough. Here's what we're seeing:

  • server response missing access token”: After what looks like a successful user sign in, token exchange failed because we got an empty access token. 
  • "invalid_request": which seems to happen when a user clicks the forgotten password link, not sure but this seems like a configuration setup on your end that needs to be handled. 
  • error processing request - Missing cookie data”: also not sure what this is regarding but seems to be cookie related. 

The team is thinking the issue you're having is related to the missing access token. There's a setting inside Entra's OIDC configuration for this (I'm attaching a screenshot of the page). Can you confirm that the “Access tokens” checkbox is selected? 

 


Hi,

I confirm that this option is currently activated in Azure B2C :


Caroline13

Then I'm afraid we've exhausted the possibilities that it's something on our end that's causing the error, we're still not seeing it in our error logs. I tried looking around Azure's documentation for the “invalid_error” message and I see it referenced here in their error codes.