feat(auth): sign in with OrangeCat — recognition, never authority - #73
Merged
Conversation
Solon gets its first and only login: NextAuth v5 with a single orangecat OIDC provider (identity scopes only), mirroring FleetCrown's proven config (client_secret_post, PKCE+state). Deliberately absent, as doctrine: - no passwords, no registration — membership is granted by vote (or the documented operator bootstrap), never by a signup form - no adapter, no auth tables — the JWT carries the OrangeCat actor id; membership is resolved fresh from members.oc_actor_id per request so a 30-day token can never outlive a roster change - no middleware — every page and API stays public; a session only adds recognition (the middleware-strangles-receivers class cannot exist here) - anonymous OrangeCat accounts are rejected at the door (governance identities must be attributable); /auth/error explains why, and the gate is pinned by unit tests Surfaces: nav sign-in control (hidden when the OAuth pair is unset; SessionProvider keeps marketing pages static), /account showing OC identity + live membership status, add-member.ts --oc-actor to link a human member to their OrangeCat identity. OC side has been ready since orangecat#661 (client registered, secrets staged in /opt/solon/shared/.env); AUTH_SECRET staged alongside. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
What
Solon's first and only login: "Sign in with OrangeCat" (NextAuth v5, single
orangecatOIDC provider, identity scopes only). Completes the deferred OC1 Solon-side item — the OC client has been registered and the secrets staged on the box since orangecat#661.Doctrine (what is deliberately absent)
members.oc_actor_idon every request, so a 30-day token can never outlive a roster change./auth/errorexplains it honestly, and the gate is pinned by unit tests.Surfaces
SessionProviderkeeps all marketing pages static — verified in build output)/account: OC identity (name/email/actor id) + live membership status, with honest copy for observersscripts/add-member.ts --oc-actor <uuid>links a human member to their OrangeCat identity (humans only; agents are recognized by API key).env.examplecreated (README referenced it but it never existed)Verification
npm run verifygreen: lint, typecheck, design:check, 33 tests (4 new pinning the anonymous gate)npm run buildgreen; static pages stayed static (○),/account+/auth/error+ auth route dynamic (ƒ)AUTH_SECRETstaged in/opt/solon/shared/.env; post-merge I'll verify the live OAuth dance end-to-end (signin → orangecat.ch/oauth/authorize with client_id=solon)🤖 Generated with Claude Code