Diagnosing invalid client ID in Authorize URLs

Questions
1

While following along https://developer.okta.com/docs/guides/add-an-external-idp/oktatookta/create-authz-url/, I noticed that when I used the wrong client ID, I (naturally) got “Bad request” responses from Okta. However, it took me quite a long time to realize that the client ID was the culprit.

Is there some way in Okta to diagnose this kind of errors? I’ve noticed that for invalid redirect URIs, the bad request error page contains a corresponding error message, but for client IDs it doesn’t. There’s also apparently no entry in the system log.

1 Like
2

Did anyone get any solution regarding this?

3

I didn’t get any answer.

4

There’s not really any way to do this, invalid client ids just throw a generic 400 error. You just need to ensure that the client ID you provide in your authorize call is correct (case sensitive!) and that the app is ACTIVE in the org you are using for the /authorize request. These details are also here.

6

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