JWT-verifier -> Unable to find a signing key that matches 'xxxx' about okta-oidc-js HOT 4 CLOSED

Right, so this is my bad on misunderstanding okta's auth servers. I need to use my company.okta.com/oauth2/default as my signin.

Will try it!

from okta-oidc-js.

Thanks for report @Pixelatex.

After logging into okta

Are you using the same issuer (https://${process.env.OKTA_DOMAIN}/default) when signing in?

Is specified 'kid' hBLe8Pk0HtpKnAeQ2LYKzA3XYhWTZJpxlkF-1OCr4bo returned from either of authorization servers endpoints?

https://${process.env.OKTA_DOMAIN}/oauth2/default/v1/keys
https://${process.env.OKTA_DOMAIN}/oauth2/v1/keys

from okta-oidc-js.

I don't really have an issuer field when I login. We are using next-auth which only accepts client_id, client_secret and domain.

The domain is company.okta.com/oauth2

oauth2/v1/keys returns hBLe8Pk0HtpKnAeQ2LYKzA3XYhWTZJpxlkF-1OCr4bo as the key while the default/ path returns a different one

from okta-oidc-js.

Tokens issued by org authorization server (company.okta.com/oauth2) can't be validated by custom authorization server (company.okta.com/oauth2/default) - you probably want to have token issued by custom authorization server during sign in. Please check out Authorization Servers doc page in case you haven't already.

from okta-oidc-js.