Ben Stull
2590c244d6
Replaces the Gitea OAuth gesture as the primary human-auth path (roadmap item #5, SPEC §6.2). Users sign in by entering their email, receiving a six-digit code via the existing SMTP layer, and entering the code on a two-step /login surface. The Gitea OAuth callback remains functional during migration — the new UI links to it as a fallback for users with active OAuth sessions or older invite paths — and is scheduled for removal in a future release once OTC adoption is universal. Existing users are linked by email on first OTC sign- in (gitea_id preserved); new users are provisioned with NULL gitea_id and rely on email as the identity key. The migration introduces backend/migrations/012_otc.sql (otc_codes table + users schema rebuild for nullable gitea_id and a partial unique index on email), two new endpoints (POST /auth/otc/request, POST /auth/otc/verify), bcrypt as a new backend dependency for code hashing, and 11 new tests in test_otc_vertical.py covering the happy path, expired and consumed and wrong codes, the per-email rate limit, the allowlist gate, the OAuth-era link path, fresh provisioning, and prior-code invalidation on re-request. No new secrets are required — the existing SECRET_KEY signs sessions and bcrypt's per-row salt covers the code hashes. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
95 lines
3.5 KiB
Bash
95 lines
3.5 KiB
Bash
# --- Gitea ---
|
|
# Base URL of the Gitea instance the app speaks to.
|
|
GITEA_URL=http://localhost:3000
|
|
|
|
# The bot service account that performs every Git operation per §1.
|
|
# Provision a real Gitea user, generate a personal access token with
|
|
# repo and admin (or at minimum: repo, write:repository) scopes, and
|
|
# put the token here. The bot is the only Git writer.
|
|
GITEA_BOT_USER=rfc-bot
|
|
GITEA_BOT_TOKEN=
|
|
|
|
# The Gitea org or user that owns the meta repo and every RFC repo
|
|
# the bot will create on graduation.
|
|
GITEA_ORG=wiggleverse
|
|
META_REPO=meta
|
|
|
|
# --- OAuth (Gitea) ---
|
|
# In Gitea: Site Administration → Applications → Add OAuth2 Application.
|
|
# Redirect URI: {APP_URL}/auth/callback
|
|
OAUTH_CLIENT_ID=
|
|
OAUTH_CLIENT_SECRET=
|
|
|
|
# --- App ---
|
|
APP_URL=http://localhost:8000
|
|
SECRET_KEY=change-me-to-a-long-random-string
|
|
DATABASE_PATH=data/rfc-app.db
|
|
|
|
# Per §1: owner zero. The Gitea login that gets the owner role on
|
|
# first sign-in.
|
|
OWNER_GITEA_LOGIN=ben
|
|
|
|
# Webhook signature secret. Gitea sends X-Gitea-Signature as the
|
|
# HMAC-SHA256 of the body using this secret. Per §4.1 the webhook is
|
|
# one of two cache writers; signing keeps spurious writes out.
|
|
GITEA_WEBHOOK_SECRET=change-me-to-a-shared-secret
|
|
|
|
# --- LLM providers (carryover §18) ---
|
|
# Comma-separated list of provider keys to enable. Per the §19.2
|
|
# per-RFC-model topic, this is app-wide until that topic lands.
|
|
ENABLED_MODELS=claude
|
|
ANTHROPIC_API_KEY=
|
|
GOOGLE_API_KEY=
|
|
OPENAI_API_KEY=
|
|
|
|
# --- Email (§15.4) ---
|
|
# Leave SMTP_HOST unset to use the stdout fallback — the integration
|
|
# tests rely on it, and a dev environment without a real SMTP provider
|
|
# still sees envelope traces in the logs. Set the rest to wire a real
|
|
# provider (Postmark, Mailgun, SES, etc.).
|
|
SMTP_HOST=
|
|
SMTP_PORT=587
|
|
SMTP_USER=
|
|
SMTP_PASSWORD=
|
|
SMTP_STARTTLS=1
|
|
|
|
# Single non-spoofing envelope identity per §15.9 — every notification
|
|
# email goes out from the same address regardless of which user's
|
|
# gesture produced it. Configure both the SPF and DKIM records for
|
|
# this address with the chosen SMTP provider.
|
|
EMAIL_FROM=notifications@wiggleverse.local
|
|
EMAIL_FROM_NAME=Wiggleverse
|
|
|
|
# §15.4 bundle threshold: when a user's quiet-hours release queue is
|
|
# at least this big, the flush goes out as one bundled "Activity while
|
|
# you were away" email instead of individual sends.
|
|
EMAIL_BUNDLE_THRESHOLD=5
|
|
|
|
# Set to 0 to suppress every outbound email (the inbox and SSE still
|
|
# work — only the email channel turns off).
|
|
EMAIL_ENABLED=1
|
|
|
|
# --- Email-bounce webhook (§15.4 + §19.2-settled) ---
|
|
# When set, `/api/webhooks/email-bounce` requires the same value in
|
|
# the `X-Webhook-Secret` header. Pick a long random string and
|
|
# configure the SMTP provider's webhook to inject it. When unset,
|
|
# the webhook stays unauthenticated for dev — the v1 contract.
|
|
WEBHOOK_EMAIL_BOUNCE_SECRET=
|
|
|
|
# --- §12 hygiene cadence (Slice 8) ---
|
|
# How often the hygiene scheduler sweeps for the 30/90-day boundaries.
|
|
# Production default is hourly; tests override to seconds via the same
|
|
# env var.
|
|
HYGIENE_TICK_SECONDS=3600
|
|
|
|
# --- v0.7.0: email + one-time-code sign-in (§6.2) ---
|
|
# How long a one-time code stays valid after issuance. Re-requesting
|
|
# invalidates the prior code immediately regardless of TTL.
|
|
OTC_TTL_MINUTES=10
|
|
|
|
# Per-email cooldown between successive /auth/otc/request calls. The
|
|
# endpoint returns HTTP 429 when the cooldown blocks a request (the
|
|
# loud-failure shape so the abuse path is visible). Set to 0 to
|
|
# disable the cooldown — useful for tests but never in production.
|
|
OTC_REQUEST_COOLDOWN_SECONDS=60
|