🐛 fix: read role from URL param on verify-email for cross-browser redirect#789
Merged
Merged
Conversation
…ks cross-browser The cookie approach broke when the verification link was opened in a different browser. Now reads ?role= from the URL (set by the backend) as the primary signal, falling back to the cookie for backwards compatibility. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
need4deed
approved these changes
Jul 12, 2026
need4deed
approved these changes
Jul 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
n4d_pending_rolecookie to decide where to redirect after verification — this broke when the link was opened in a different browser?role=from the URL (set by the backend) as the primary signal; cookie remains as a fallback for links sent before this deployTest plan
/register/agent/completeform, not login?role=param, cookie present) still redirect correctly via the cookie fallback🤖 Generated with Claude Code