Files
crosscode-platform/apps/accounts/README.md
T
joshuaandClaude Opus 5.5 fdd53ae4db Accounts: Playwright on the real pages; interaction cookie path fix
The interaction address is now /api/v2/interaction/<uid> (redirecting to
the sign-in page): oidc-provider scopes its cookie to that path, so every
step's API call gets it. Before, a real browser never sent it and every
sign-in 'expired'; the test browser now honours cookie paths too.
8 Playwright tests (deep link, wrong password, foreign return address,
sign-up, reset mid-sign-in, 2FA set-up, account page, admin) on the real
backend with an in-memory database, no Postgres needed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-18 15:01:32 +02:00

1.5 KiB

Accounts

The church's sign-in for every Cross Code product (ROADMAP-v3 §3, phase 3; plan and decisions in docs/ACCOUNTS-1.0-PLAN.md). A small OpenID Connect provider per church at accounts.<address>: people sign in once and are signed in to all the church's products, coming back to the page they started on. Members never see it as a product; admins manage people, sign-in settings, linked products and the church profile here.

  • backend/: Express + oidc-provider 9 + Prisma (ES modules). npm run dev, npm test (Node's test runner through tsx: the whole app against an in-memory database, with a test product on openid-client), npm run build.
  • frontend/: Next.js 16 pages (sign-in steps, account page, admin, setup), strict CSP with a nonce per page, the church's colours from its profile.
  • e2e/: Playwright on the real pages (npx playwright test in apps/accounts): the backend on an in-memory database with a test product (e2e/server.ts), Next on 3210. No database needed.
  • Roles stay in each product: Accounts only knows who someone is (plan §2, "Roles stay in each product").
  • Products sign in with @crosscode/auth-client (packages/auth-client).

Local development: Postgres in backend/.env (DATABASE_URL, ACCOUNTS_URL=http://localhost:3200, LINKS_ALLOW_PRIVATE=true), npx prisma migrate deploy, then npm run dev in both folders (the frontend runs on 3200 with next dev -p 3200 and sends /api to the backend on 5200).