<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00009IMzdTCATOkta Classic EngineSingle Sign-OnAnswered2024-07-20T09:09:16.000Z2023-06-08T08:30:29.000Z2023-06-09T16:01:13.000Z

yfhks (yfhks) asked a question.

invalid client/no client credentials found when loggin into an application using OKTA

Hi, since 3 weeks (11 may) I am getting an error when I use OKTA to login to an application (OIDC). It always worked fine, but now it returns the following message after debugging: "invalid client/no client credentials found"

 

Is anyone familiar with this issue? What could it be that is suddenly started to produce these messages?

 

 We provide the following parameters int the body of the request (first line is the URL of the request)

Image is not available


  • User16594883467582706479 (Customer Support Online Experience)

    Hi, @yfhks (yfhks)​ 

     

    Thank you for posting on our Community page!

     

    My advice would be to leverage the Okta Developer forums for this type of questions and take advantage of their expertise.

    https://devforum.okta.com/

     

    Thank you for reaching out to our Community and have a great day!

    _____________________________________________________________________________

    Coming soon: Get tips from community managers during Okta Community's first Ask Me Anything event on 6/22

    _____________________________________________________________________________

    Community members help others by clicking Like or Select as Best on responses. Try it today.

    _____________________________________________________________________________

    Expand Post
  • NiallM.34104 (Atlas Identity)

    Okta is giving you the answer, you just need to dig a little deeper. In short, something has changed if it previously worked. If you are sure the application configuration in Okta hasn't changed, I would check the URL endpoints you are using.

  • NiallM.34104 (Atlas Identity)

    It's sometimes easier to debug outside of your application. My go to is this: https://oidcdebugger.com/. Make sure you add the debugger URL endpoint as a redirect URI in your Okta client, then hack away at it.

This question is closed.
Loading
invalid client/no client credentials found when loggin into an application using OKTA