Facebook provider not working - next-auth v4.0.0-beta.4
See original GitHub issueDescription 🐜
Seems the “state” query param is lost in between request. I did some light debugging it seems that the error originates from node-openid-client
I saw that it had specific node.js requirements, but I do seem to meet them (14.18.0)
My current simple setup:
Error that I’m getting with (Debug enabled + additional logging):
Is this a bug in your own project?
No
How to reproduce ☕️
Just a simple setup as in the example.
Facebook login callback setting:
Screenshots / Logs 📽
No response
Environment 🖥
System: OS: macOS 10.15.7 CPU: (12) x64 Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 198.18 MB / 16.00 GB Shell: 5.7.1 - /bin/zsh Binaries: Node: 14.18.0 - ~/.nvm/versions/node/v14.18.0/bin/node Yarn: 1.22.5 - ~/.yarn/bin/yarn npm: 6.14.15 - ~/.nvm/versions/node/v14.18.0/bin/npm Browsers: Chrome: 94.0.4606.71 Edge: 94.0.992.38 Firefox: 90.0.2 Safari: 14.0 npmPackages: next: ^11.1.2 => 11.1.2 next-auth: ^4.0.0-beta.4 => 4.0.0-beta.4 react: 17.0.2 => 17.0.2
Contributing 🙌🏽
Yes, I am willing to help solve this bug in a PR
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (2 by maintainers)
Apparently, there was a plugin that was messing with “req.url” which then in turned caused
client.callbackParams(req)
to malfunction and auth flow to fail. Sorry for the bother.Yeah, I saw #2524 which is why I doubled checked if I’ve done everything according to docs. I also tried playing around with configuration settings like
checks
, setting it topkce
ornone
, but in that case, I’m getting a 401.As per your request @balazsorban44 , I have just checked with Safari(14.0) and Firefox (92.0), but I’m getting the same error.