id_token not present in TokenSet

[jimfilippou]

Hello I am trying to get Okta provider to work with next-auth but I am getting this issue on the callback step.

https://next-auth.js.org/errors#oauth_callback_error id_token not present in TokenSet

My next-auth configuration looks like this

const options: NextAuthOptions = {
    providers: [
        OktaProvider({
            clientId: process.env.OKTA_CLIENTID,
            clientSecret: process.env.OKTA_CLIENTSECRET,
            issuer: process.env.OKTA_ISSUER,
        })
    ],
    theme: {
        colorScheme: "auto",
        brandColor: ""
        logo: ""
    },
    pages: {
        signIn: '/auth/login',
        error: '/auth/error'
    },
    secret: "secret",
}

const auth = (req, res) => NextAuth(req, res, options);

export default auth;

Anyone know what would be the cause? Thanks for your time and happy new year! 🥳

[balazsorban44]

@bogdansoare changed the default config to assume there is an id_token present in #3418, but it sounds like something might need to be configured in Okta. @bogdansoare any ideas?

[balazsorban44]

Here are the default scopes:

next-auth/src/providers/okta.ts

Line 45 in c71cb84

authorization: { params: { scope: "openid email profile" } },

Which one is missing?

You also link to an Auth0 forum, but you mention the Okta provider. Am I missing something? 🤔

[jimfilippou]

Doesn't look like something's missing. Also I want to add that authentication works when I do a refresh or manually go to a protected URL. As it seems, the only issue is the callback

[bogdansoare]

@jimfilippou I didn't do any additional configuration in Okta, the default scopes worked out of the box

[paulv317]

I am having an issue with the callback when I specifically do not send scope as a parameter to Okta. I have Okta set up to handle a request without the scopes parameter, and it should then look at the Group a user is in, and return the scopes for that user in the jwt. Per Okta documentation this should be allowed: https://developer.okta.com/docs/guides/customize-authz-server/main/#create-scopes - subheading #6. Any thoughts @balazsorban44 ?

[paulv317]

https://next-auth.js.org/errors#oauth_callback_error id_token not present in TokenSet {
error: [Error [OAuthCallbackError]: id_token not present in TokenSet] {
code: undefined
},
providerId: 'okta',
message: 'id_token not present in TokenSet'
}

This is the error I am getting.

[robertgiannini]

I was getting this issue due to the scope param when attempting to login with Google. In a previous version of Next.js, you were supposed to pass in the scopes as a string separated by spaces, but in the lastest version of Next.js (as of this comment) you are supposed to pass an array of scope strings. This behavior was cause by an update to my Next.js version.

[peter-olom]

I arrived at this problem just by updating next-auth. I remained on version 4.0.6 for a long time now. After seeing your response, I deleted the authorization prop which contained my scope and I was fine afterwards. I used the AzureAD provider. Thanks

[achinth]

Any solution to fix this issue?

[matheuslemke]

This worked for me:

          Google is an OIDC provider, make sure you include `openid` in scopes.

Originally posted by @balazsorban44 in #4295 (comment)

[syedamanat]

Worked for me as well.