Define signup, invitations, and OAuth account identity #8
Labels
No labels
needs-info
needs-triage
ready-for-agent
ready-for-human
wayfinder:grilling
wayfinder:map
wayfinder:prototype
wayfinder:research
wayfinder:task
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#11 Choose the application architecture and deployment contract
MISChaufen/prevouch
#12 Evaluate member and admin journeys in four live-switchable designs
MISChaufen/prevouch
Reference
MISChaufen/prevouch#8
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #1
Question
How do signup controls, invitations, and OAuth login interact, and what identifies one member account?
Preserve open, disabled, and invitation-only signup; one-use, finite-use, and unlimited invitations via both codes and URLs; OAuth2 login creating a missing account even when signup is disabled. Decide the OAuth behavior in invitation-only mode, which configured providers qualify, whether creating an account also grants event access, and administrator bootstrap/roles.
Settle local login and email verification expectations, invitation use counting and concurrent redemption, expiry/revocation, provider identity keys, absent or unverified provider emails, and safe explicit account linking when email addresses match. Distinguish authentication, account creation, and permission to join a queue. Resolve with rules and examples, leaving vendor selection to architecture.