Okta user Authorization non API

[andrew.rands]

I ran in to the same problem. The examples from Okta all rely on the API Access Management module (API Access Management Platform - Secure API Access | Okta) which we haven’t bought.

I found that I could get the code to work once I modified the security issuer URL. Where in the example it states

issuer: ‘https://{yourOktaDomain}/oauth2/default’,

I used

issuer: ‘https://{yourOktaDomain}’,

and it seemed to work.

See

CORS error in production

I’ve created a React/Dot Net Core SPA. It works fine in a development environment. Have now created an SPA application in our production environment & am getting a CORS error: “Access to XMLHttpRequest at ‘https://ZZZZZZZZ/oauth2/default/.well-known/openid-configuration’ from origin ‘https://localhost:44381’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource.” I have added https://localhost:44381 as a CORS trusted origin. (The error be…