You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all, I've run into a few times during production that my users couldn't log in. Last night I switched the subdomain of my web portal (redirected the old subdomain to a new one). While I was testing everything seems fine. But this morning some users starts complaining that they cannot sign in, even though a lot others could. I was able to reproduce that but I didn't have the time to do a full investigation of why it happened. What are some of the ways to quickly help users recover in next-auth?
I'm using the gmail and azure provider.
I tried deleting the session object, but it didn't seem to trigger recreating session.
I tried to deleting the account object, which didn't seem to resolve the issue either.
I then tried deleting the user object. Then users are recreated as user log in and then everything is working from that point onwards.
I still suspect that it is related to some session and cookie combinations. But why would clearing out the session object not trigger recreating the session from the same user?
Sorry that I only have pieces of the info, but I wonder if someone has run into that before and has more insights.
Thanks in advance!
How to reproduce ☕️
No clear way of reproducing.
Contributing 🙌🏽
Yes, I am willing to help answer this question in a PR
questionAsk how to do something or how something works
1 participant
Converted from issue
This discussion was converted from issue #4690 on June 10, 2022 13:50.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Question 💬
Hi all, I've run into a few times during production that my users couldn't log in. Last night I switched the subdomain of my web portal (redirected the old subdomain to a new one). While I was testing everything seems fine. But this morning some users starts complaining that they cannot sign in, even though a lot others could. I was able to reproduce that but I didn't have the time to do a full investigation of why it happened. What are some of the ways to quickly help users recover in next-auth?
I'm using the gmail and azure provider.
I tried deleting the session object, but it didn't seem to trigger recreating session.
I tried to deleting the account object, which didn't seem to resolve the issue either.
I then tried deleting the user object. Then users are recreated as user log in and then everything is working from that point onwards.
I still suspect that it is related to some session and cookie combinations. But why would clearing out the session object not trigger recreating the session from the same user?
Sorry that I only have pieces of the info, but I wonder if someone has run into that before and has more insights.
Thanks in advance!
How to reproduce ☕️
No clear way of reproducing.
Contributing 🙌🏽
Yes, I am willing to help answer this question in a PR
Beta Was this translation helpful? Give feedback.
All reactions