Skip to content

Plans Authentication

Ankit Upadhyay edited this page Jul 24, 2026 · 2 revisions

Plans: Authentication

Moving auth off external providers and hardening web sign-in. Architecture context: Authentication and Identity and ADR-0003.

SuperTokens migration

Canonical source: supertokens-migration.md Status: core migration merged — PR #1763 (2026-07-16); epic #1672 stays open for follow-ups (passkeys/MFA rollout, legacy grace-window removal).

Replaced AWS Cognito (email/OTP) and Firebase (social) with self-hosted SuperTokens in apps/backend, apps/frontend, and apps/mobileAppYC, behind a feature flag with a dual-verify period (residual legacy tokens accepted during cutover under AUTH_LEGACY_TOKEN_GRACE). The migration established a provider-neutral auth boundary — requireWebAuth replaced authorizeCognito — so the provider is a swappable adapter. The seven-role RBAC model was preserved. Decision record: ADR-0003.

Passkeys, MFA / 2FA (web PIMS)

Canonical source: pms-web-passkey-mfa-2fa-implementation-guide.md

A Postgres-first plan to add:

  • Apple / WebAuthn passkey sign-in for the web PIMS,
  • MFA / 2FA for password logins,
  • and broader auth hardening and observability across apps/frontend + apps/backend.

Designed to layer on top of the provider-neutral boundary above rather than being wired to a specific vendor.

Related

Product & Domain
Architecture
Applications
Design & Accessibility
Engineering Handbook
Decisions (ADRs)
Design Docs & Plans
Roadmap
Operations
Meta

Canonical code & docs: main repo · Auto-generated companion: DeepWiki

Clone this wiki locally