Using Okta Provider after v3.20

[slapner]

Has anyone been able to use Okta as a provider since the 3.2.0 release? My application was working fine before the url patterns changed in NextAuth and now I only get a 404 when I try to sign-in.

[balazsorban44]

#1257 could this be related, or the issue occurs in stable 3.2.0 already?

I'm that case, #1022 here is the one that could have caused issues. Do you think I overlooked something?

[slapner]

Finally just figured out that I need to append /oauth2 to my Okta domain variable.

[slapner]

I think the change you made is correct because not all orgs use the same authorization endpoint but maybe adding a note in the documentation could help people in the future

[iaincollins]

@slapner Thanks for the insights!

Do you have any specific recommendations / example usage we could add to the documentation?

Do you think the defaults should be different from what they currently are?

It's hard to keep track of best practice with some providers,especially when there are multiple ways of using some of them (e.g. Okta, Keycloak, Azure) so any insight or links to relevant documentation or official examples are most welcome.

[slapner]

@iaincollins I think the confusion might come from the parameter being called 'domain'

In the Okta admin panel there is a 'Okta Domain' that you can copy with one click (like the clientId, secret) so if someone does that and doesn't add '/oauth2' (at minimun) after their domain then it will not work. Maybe just a note about checking the AuthorizationUrl pattern for their organization? Most people will just have '/oauth2' but others may have more.

[brandonchinn178]

ah! I wrote an issue for this: #1345

I think it would be helpful to rename domain to baseUrl, to correspond with Okta's documentation, as well as how @okta/jwt-verifier has you configure the Okta URL

e.g. I currently do

domain: `${process.env.OKTA_DOMAIN}/oauth2/default`,

but I think it would be better as

baseUrl: `https://${process.env.OKTA_DOMAIN}/oauth2/default`,