Replies: 1 comment 3 replies
-
Ok, when the live demo was working earlier this morning, I tried on safari 15 with the GitHub oauth provider and ran into the same issue. I went through the login dance, but when redirected back, I was not logged in. I can't see the logs to confirm, but it is almost certainly the same issue. Github auth worked fine in the demo in brave. So... it looks like the cookies necessary to complete the oauth flow are not available for some reason in safari 15. It almost seems like safari is treating the same-site lax setting incorrectly or something. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm trying to characterize a strange bug I'm running into only on safari 15.
I have next-auth
^4.0.2
with custom login pages in my next app. Everything works great on chrome and firefox.When try try to log in with the GitHub provider, I get the following error:
When I debug these different code paths, it comes down to what appears to be the
req.cookies
object being unavailable when GitHub redirects back to my app, but only in safari. The state cookie is set tosame-site
lax
, which seems to work fine in chrome and firefox, but not in safari. When safari is redirected back, it refuses to share any of thelax
cookies strangely. If I force the cookies to be same sitenone
GitHub login works in safari.So... anyone know why safari is refusing to share cookies with next-auth when it redirects back from Github?
Beta Was this translation helpful? Give feedback.
All reactions