Investigate login verification loop issue #1901
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Normalize URL origins in
isValidVerificationUrl
to fix a login verification loop.The previous comparison
urlObj.origin !== process.env.NEXTAUTH_URL
failed whenprocess.env.NEXTAUTH_URL
included a trailing slash, asurlObj.origin
never has one. This mismatch caused the verification to fail and users to get stuck in a login loop. The fix ensures both URLs are normalized to their origin before comparison.Slack Thread