Azure - AD - id_token not present in TokenSet

[crhampton1]

Having some issues getting Azure-Ad provider working.

I have followed every step at https://next-auth.js.org/providers/azure-ad.

It loads the login screen and allows me to log in, but then I receive a callback_oauth_error with the message "it_token not present in TokenSet". I don't see that explained at all in the instructions, so hoping someone here has come across that and has some ideas? Happy to provide any information you need! I am sure I am just missing something.

Thanks

https://next-auth.js.org/errors#oauth_callback_error id_token not present in TokenSet { error: { message: 'id_token not present in TokenSet', stack: 'TypeError: id_token not present in TokenSet\n' + ' at Client.validateIdToken (/Users/christopherhampton/Documents/GitHub/wncc/node_modules/openid-client/lib/client.js:755:15)\n' + ' at Client.callback (/Users/christopherhampton/Documents/GitHub/wncc/node_modules/openid-client/lib/client.js:484:18)\n' + ' at processTicksAndRejections (node:internal/process/task_queues:96:5)\n' + ' at async oAuthCallback (/Users/christopherhampton/Documents/GitHub/wncc/node_modules/next-auth/core/lib/oauth/callback.js:112:16)\n' + ' at async Object.callback (/Users/christopherhampton/Documents/GitHub/wncc/node_modules/next-auth/core/routes/callback.js:50:11)\n' + ' at async NextAuthHandler (/Users/christopherhampton/Documents/GitHub/wncc/node_modules/next-auth/core/index.js:133:28)\n' + ' at async NextAuthNextHandler (/Users/christopherhampton/Documents/GitHub/wncc/node_modules/next-auth/next/index.js:20:19)\n' + ' at async Object.apiResolver (/Users/christopherhampton/Documents/GitHub/wncc/node_modules/next/dist/server/api-utils.js:102:9)\n' + ' at async DevServer.handleApiRequest (/Users/christopherhampton/Documents/GitHub/wncc/node_modules/next/dist/server/base-server.js:1076:9)\n' + ' at async Object.fn (/Users/christopherhampton/Documents/GitHub/wncc/node_modules/next/dist/server/base-server.js:963:37)', name: 'TypeError' }, providerId: 'azure-ad', message: 'id_token not present in TokenSet' } [next-auth][error][CALLBACK_OAUTH_ERROR] https://next-auth.js.org/errors#callback_oauth_error id_token not present in TokenSet TypeError: id_token not present in TokenSet at Client.validateIdToken (/Users/christopherhampton/Documents/GitHub/wncc/node_modules/openid-client/lib/client.js:755:15) at Client.callback (/Users/christopherhampton/Documents/GitHub/wncc/node_modules/openid-client/lib/client.js:484:18) at processTicksAndRejections (node:internal/process/task_queues:96:5) at async oAuthCallback (/Users/christopherhampton/Documents/GitHub/wncc/node_modules/next-auth/core/lib/oauth/callback.js:112:16) at async Object.callback (/Users/christopherhampton/Documents/GitHub/wncc/node_modules/next-auth/core/routes/callback.js:50:11) at async NextAuthHandler (/Users/christopherhampton/Documents/GitHub/wncc/node_modules/next-auth/core/index.js:133:28) at async NextAuthNextHandler (/Users/christopherhampton/Documents/GitHub/wncc/node_modules/next-auth/next/index.js:20:19) at async Object.apiResolver (/Users/christopherhampton/Documents/GitHub/wncc/node_modules/next/dist/server/api-utils.js:102:9) at async DevServer.handleApiRequest (/Users/christopherhampton/Documents/GitHub/wncc/node_modules/next/dist/server/base-server.js:1076:9) at async Object.fn (/Users/christopherhampton/Documents/GitHub/wncc/node_modules/next/dist/server/base-server.js:963:37) { name: 'OAuthCallbackError', code: undefined }

[Rodeveer]

Following. I've got the same issue since a few days actually. Last week it did work fine.
In the AzureADProvider in providers I tried to set idToken: false. Solves the error, doesnt log me in 😞

I've created an issue since I'm experiencing this also on a clean example: #3627

[Fremmedkar]

Might be a problem with next-auth version 4.1.0

Version 4.0.6 works with Azure AD

[crhampton1]

Thank you @Fremmedkar. Can confirm that downgrading to 4.0.6 exactly allows me to use Azure to login! Glad to know I was doing everything right.

@Rodeveer, I will comment on that ticket too. I had assumed it was an issue with me and not a bug. Thank you!!