no access token provided

[m10rten]

Hi everyone,

Im pretty new to the OAuth world, but I know that you sometimes need a refresh_token / access_token.

Context: I am working on some Github OAuth with next-auth and everything was working fine locally: I made a local OAuth app on Github, made sure I had the secret and id in my .env and It worked as expected: I was able to log in.
But once I pushed it to vercel, it stopped working, first I had to put in a secret within the NextAuth section,
* I did put the env values of the project within the vercel env(vercel project is from correct URL: production URL). local URL and vercel URL have different Github OAuth apps.
OK, fixed that, then this happend:

https://next-auth.js.org/errors#oauth_callback_error no access token provided {
  error: {
    message: 'no access token provided',
    stack: 'TypeError: no access token provided\n' +
      '    at Client.requestResource (/var/task/node_modules/openid-client/lib/client.js:1121:13)\n' +
      '    at Client.userinfo (/var/task/node_modules/openid-client/lib/client.js:1233:33)\n' +
      '    at Object.request (/var/task/node_modules/next-auth/providers/github.js:27:38)\n' +
      '    at oAuthCallback (/var/task/node_modules/next-auth/core/lib/oauth/callback.js:126:41)\n' +
      '    at processTicksAndRejections (node:internal/process/task_queues:96:5)\n' +
      '    at async Object.callback (/var/task/node_modules/next-auth/core/routes/callback.js:50:11)\n' +
      '    at async NextAuthHandler (/var/task/node_modules/next-auth/core/index.js:186:28)\n' +
      '    at async NextAuthNextHandler (/var/task/node_modules/next-auth/next/index.js:23:19)\n' +
      '    at async /var/task/node_modules/next-auth/next/index.js:59:32\n' +
      '    at async Object.apiResolver (/var/task/node_modules/next/dist/server/api-utils/node.js:179:9)',
    name: 'TypeError'
  },
  providerId: 'github',
  message: 'no access token provided'
}

I looked on Github for likewise issues or bugs, I even looked into the node_modules to trace where it came from, long story short: provider gets params, params get extracted into tokens, tokens get send to client (openid-client) and this throws the error shown above.

Any suggestion is appreciated!
Thanks in advance.

[davidlashlee]

hey im having the same problem on local. did you ever figure this out?

[davidlashlee]

got mine to work, i made a github app client instead of a github oauth app on github -> settings -> developer settings. argh!

[treipatru]

Posting here since I'm having a similar error in 2023 and found this discussion via web search. I have a different call stack.

https://next-auth.js.org/errors#oauth_callback_error no access token provided {
  error: TypeError: no access token provided
      at Client.requestResource (webpack-internal:///(rsc)/./node_modules/.pnpm/openid-client@5.4.3/node_modules/openid-client/lib/client.js:1017:19)
      at Client.userinfo (webpack-internal:///(rsc)/./node_modules/.pnpm/openid-client@5.4.3/node_modules/openid-client/lib/client.js:1109:37)
      at Object.request (webpack-internal:///(rsc)/./node_modules/.pnpm/next-auth@4.22.5_next@13.4.13_react-dom@18.2.0_react@18.2.0/node_modules/next-auth/providers/github.js:21:46)
      at oAuthCallback (webpack-internal:///(rsc)/./node_modules/.pnpm/next-auth@4.22.5_next@13.4.13_react-dom@18.2.0_react@18.2.0/node_modules/next-auth/core/lib/oauth/callback.js:127:47)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async Object.callback (webpack-internal:///(rsc)/./node_modules/.pnpm/next-auth@4.22.5_next@13.4.13_react-dom@18.2.0_react@18.2.0/node_modules/next-auth/core/routes/callback.js:18:79)
      at async AuthHandler (webpack-internal:///(rsc)/./node_modules/.pnpm/next-auth@4.22.5_next@13.4.13_react-dom@18.2.0_react@18.2.0/node_modules/next-auth/core/index.js:202:38)
      at async NextAuthRouteHandler (webpack-internal:///(rsc)/./node_modules/.pnpm/next-auth@4.22.5_next@13.4.13_react-dom@18.2.0_react@18.2.0/node_modules/next-auth/next/index.js:50:30)
      at async NextAuth._args$ (webpack-internal:///(rsc)/./node_modules/.pnpm/next-auth@4.22.5_next@13.4.13_react-dom@18.2.0_react@18.2.0/node_modules/next-auth/next/index.js:84:24)
      at async eval (webpack-internal:///(rsc)/./node_modules/.pnpm/next@13.4.13_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/server/future/route-modules/app-route/module.js:254:37) {
    name: 'OAuthCallbackError',
    code: undefined
  },
  providerId: 'github',
  message: 'no access token provided'
}

I had been running multiple app tests with same GH client id and key. The way I fixed it was to re-create a fresh OAuth application and use new credentials. 🤷 Running on next 13.4.13 (with app router) and next-auth 4.22.5.

[294916437]

Hey, I got the same problem like you that local test is normal,but got errors when deployed on the Vercel

[abarnes]

Same issue. I did create a fresh app, and it worked. Doesn't make sense to me yet why that fixed it, but it did