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
Quick question: In the guides, we are creating a session, setting the session cookie, and redirect to a (I guess) protected page. Wouldn't it add another security layer if we would do none of the above and just redirect the user to the login page? This way, even though it would have been somehow possible for someone to maliciously guess a verification token, the malicious actor would not know the associated account.
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.
-
Quick question: In the guides, we are creating a session, setting the session cookie, and redirect to a (I guess) protected page. Wouldn't it add another security layer if we would do none of the above and just redirect the user to the login page? This way, even though it would have been somehow possible for someone to maliciously guess a verification token, the malicious actor would not know the associated account.
Beta Was this translation helpful? Give feedback.
All reactions