How do I properly set up an oauth 2 authorization server?

Loading

Skip to Navigation Skip to Main Content

Search

Search

Select Language

0D50Z00008G7VhNSAVOkta Classic EngineAdministrationAnswered2018-09-05T01:28:12.000Z2018-06-30T20:50:52.000Z2018-07-16T16:28:30.000Z

00ueka75c0uDyBD4n0h71.524171454455942E12 (Customer) asked a question.

Edited by varun.kavoori1.5210444522562532E12 September 5, 2018 at 1:20 AM

How do I properly set up an oauth 2 authorization server?

I am attempting to set up a service secured by client credentials following https://developer.okta.com/blog/2018/02/01/secure-aspnetcore-webapi-token-auth.

Upon completing the code, I recieve the "Unable to retrieve access token from Okta" exception defined in the OktaTokenService.

Debugging, I discovered the response is BadRequest, so I decided to take a look at the default authorization server.

With the default authorization server I first notice there is no access_token scope defined, so I defined one.

Following that, I tried the token preview from the configured client using client credentials and the new scope, but get and Internal Server Error.

What am I missing here?

fabian.bahna1.5102194373023474E12 (Okta, Inc.)
Edited by varun.kavoori1.5210444522562532E12 September 5, 2018 at 1:27 AM
Hi Marcus,

Is this error one that you can reproduce reliably, or a one-time event? If it can be reproduced, then I recommend opening up a case with Customer Support, to troubleshoot further.

I tried to look into the error for a quick fix, however there are a lot of factors we need to check like the request format for example.

I added a documentation link below that should help, in case you missed it.

https://help.okta.com/en/prod/Content/Topics/Security/API_Access.htm
Expand Post
00ueka75c0uDyBD4n0h71.524171454455942E12 (Customer)
Edited by varun.kavoori1.5210444522562532E12 September 5, 2018 at 1:28 AM
Hi Fabian,

This issue is reproducible with a freshly created authorization server and I have opened a support ticket, per your recommendation.

Request format should be irrelevant, as I am getting the Internal Server Error using Okta's own token preview mechanism when I test selecting my app, client_credentials, and my test_scope.

This doesn't seem to be a policy issue, as restricting policy further gives a message stating the policy failed, rather than an Internal Server Error.

I did take a look at the authorization server docs, but found nothing wrong with my default or test setups that I could see.
Expand Post

This question is closed.

Recommended content

Forum

How do I debug an Okta Workflow OAuth 2.0 (Authorization Code) Test Connection Issue?

Forum

Is It Possible to Use Okta as an Authorization Server in an OAuth 2.0 Flow for Server-to-Server Requests?

Forum

Oauth 2 OIDC SSO without authorization server

Forum

how do i set up a new RSA token for an external user

Loading

How do I properly set up an oauth 2 authorization server?