R{
“error”: “invalid_request”,
“error_description”: “server responded with an error in the response body”
}eady to post?
First try searching for your answer.
Welcome to the Auth0 Community!
I understand that you have setup an Enterprise OIDC Connection, but you are getting the mentioned error message. This seems a very generic one, so a couple of steps that I suggest taking would be:
- check the logs on the IdP side, if you have access to them. These would be very helpful in figuring out the issue;
- confirm that the Client ID is set correctly;
- generate a new Client Secret and set it one more time;
- make sure the Callback URL/Redirect URI are exact matches, so they successfully point to the correct path;
- do the same with the Discovery URL, make sure it’s correctly set;
- verify that the scopes you are requesting exactly match the ones that the IdP’s client application is set to allow.
I’m also adding some useful documentations that I recommend reading through:
- Connect to OpenID Connect Identity Provider
- Enterprise Connections
- How to Enable the OIDC Logout URL in the Discovery URL
Hope this helped!
Gerald
If you can’t log in after creating an Enterprise OIDC connection, first check that the Redirect URI/Callback URL and Discovery URL are identical in both your application and your Identity Provider (IdP) settings. If they match, verify that the Client ID and Client Secret are correct and that the requested scopes are valid. If the issue continues, check the logs on both your application and the IdP for specific error messages to identify mismatches, such as client authentication methods or missing user claims.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.