Enabling /default/ routing for Applications

Questions
,
1

We are using Passport’s OIDC Connect to connect to Okta with the following configuration:

const issuer = `https://${oktaDomain}/oauth2/default`;
const callbackURL = `https://${hostname}/auth/openid/login/`;
  
const strategy = {
    issuer,
    authorizationURL: `https://${oktaDomain}/oauth2/default/v1/authorize`,
    tokenURL: `https://${oktaDomain}/oauth2/default/v1/token`,
    userInfoURL: `https://${oktaDomain}/oauth2/default/v1/userinfo`,
    clientID: clientID,
    clientSecret: clientSecret,
    callbackURL,
    scope: 'openid profile groups'
  };

However, that no longer works because of the API changes detailed here. Is there any way for us to change our app settings in Okta so that we can continue to hit the old oauth2/default/v1 API endpoints and maintain old functionality without requiring code changes?

As a follow up, I changed the strategy values to look like:

{
    issuer: `https://${oktaDomain}`,
    authorizationURL: `https://${oktaDomain}/oauth2/v1/authorize`,
    tokenURL: `https://${oktaDomain}/oauth2/v1/token`,
    userInfoURL: `https://${oktaDomain}/oauth2/v1/userinfo`,
    clientID: clientID,
    clientSecret: clientSecret,
    callbackURL,
    scope: 'openid profile groups'
  };

but I am getting a 404 Not Found error when I am redirected to the oktaDomain/oauth2/v1/authorize?response_type=code&client_id=……. endpoint.

My Application that I have created in the Applications dashboard in the Okta UI is a Single Page Application, has no Login URI set, we have https://myHostname/auth/openid/login/ listed in our Allowed Callback URLs for our apps, and a logout URL that just bounces us back to https://hostname.

In addition, refering to the developer guides, I am not seeing an option to choose the OIDC - OpenID Connect as the Sign-in method

2

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