Cannot get openid-configuration

I have one OIDC application that it is possible to log in with, and one OIDC application which cannot log in. I don’t know what the difference in settings are, but I want to find out.

I am using the okta react package for this, I can see that the application that can not log in is requesting the url /oauth2/default/.well-known/openid-configuration, which is getting a 401 as a response, along with some CORS issue on that route (maybe because of 401?). The other application is not requesting this url at all. Why is there a difference here? Some settings perhaps?

Are both apps using the same Issuer value? If you make a request to the discovery endpoint using curl or Postman, what do you see?

Hi @okra-okta ! I just resolved the issue. The issue was that one of the issuer url did not use the default value of /oauth2/default which was always added to the url in our implementation. The other issue, which was that the url was not always called, was simply because it was cached in the browser, which I did not know at the time of writing the first post.

Thanks anyway!

1 Like

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.