JordanG.28047 (Customer) asked a question.
In our Okta instance, we are attempting to add our application as an OpenID Connect Identity Provider. We have configured the Identity Provider in our Okta instance and updated our Okta Login screen to show the sign-in button for this custom provider.
The flow to our OAuth process works fine, and we are redirecting the user back to Okta. We can see from our logs that Okta is successfully making a request to our callback endpoint and getting a 200 response with an access token. The form of our response follows the OpenID specification and has a key for access_token and id_token.
However, we receive an error message upon redirecting to Okta, and the logs in Okta are showing the following error message.
Hi @JordanG.28047 (Customer),
Thank you for posting on the Okta community page!
I have done some research and it seems that this error is commonly caused by a misconfiguration, for example the usernames not being a match. I would recommend to re-visit the configuration and make sure that everything is configured properly as per your organisation needs.
Additionally, my advice would be to also leverage the Okta Developer forums for this type of questions and take advantage of their expertise.
I hope the above information is helpful!
------------------------------------------------------------------------------------------------------------------------------------------------
The October issue of the Okta Community is here and packed with tips on certification, how to earn badges, and new releases. Let us help you stay connected.