docs: Slice 2a Accounts & Identity design spec#28
Merged
Conversation
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
1 participant
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.
Design spec for Slice 2a — Accounts & Identity (the first half of Slice 2, Sharing & Accounts).
Scope: public multi-user accounts on ASP.NET Core Identity + cookie auth; PostgreSQL with EF migrations adopted; custom minimal-API auth endpoints + hand-authored vanilla-JS screens; per-user data isolation; full account lifecycle (register, verify, login, reset, change email/password, delete, lockout, remember-me).
Stress-tested across security / privacy / accessibility / loopholes — 12 findings folded into the spec (session invalidation, login enumeration, token handling, unverified-account lifecycle, a privacy/legal section, auth-screen a11y, and lifecycle edge cases).
Direction confirmed by both owners; opening for sign-off review before the implementation plan.