Repository navigation
AUTH-MAIL-002C2: handle verification links safely - #195
Merged
Merged
Conversation
✅ Deploy Preview for luminous-fox-7c393f ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This was referenced Jul 14, 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.
Outcome
Adds a safe, verification-only
/auth/actionsource route. Opening the link—including a mail scanner opening it—does not check or apply the one-time code. A person must choose Verify email first.VERIFY_EMAILbefore one apply.Safety boundary
This is verification-only source. Firebase uses one project-wide custom handler for verification, password reset, and email recovery. Do not configure this route as that global handler until every enabled mode is safely implemented, or retain Firebase's existing multi-mode handler. See the official Firebase custom-handler design.
Verification proves control of an email address only. It never grants membership, dues/payment status, discounts, roles, or officer access; it writes no Firestore data and calls no Function.
Verification
Exact source commit:
1eae2d14917406cd9ee5e05224c07ac47d1558aeExact staged diff SHA-256:
8d82d831b734ba75823fa70cb447b6b07b668ed3436f34949412963567000180Officer handoff
Officer impact: Members get one plain, deliberate verification action. Officers never request, copy, open, or screenshot a member's private link, code, or email address.
Officer documentation:
docs/officers/EMERGENCY_AND_RECOVERY.md,docs/officers/EVENTS_SHOP_MEMBERS.md, anddocs/officers/SYSTEM_MAPS.md; system/security/operations status maps are updated too.Deployment evidence: Source/tests/merge only at PR creation. No website publication,
runmprc.comverification, Firebase deployment, custom-handler/template/sender/DNS change, mailbox test, member-data action, or live behavior is claimed. Protected production release remains separately blocked on #133/#136 provider and environment configuration.Closes #194