Repository navigation
v1.2.0 — Passwordless passkey sign-in
What's new
Sign in with a passkey — no password required.
- Passwordless passkey sign-in. The login page now has a single Sign in with a passkey button. It opens the browser's discoverable-credential picker (Touch ID / Face ID / Windows Hello / security key) and signs the admin straight in — no email, no password, no second step. The passkey itself is the multi-factor credential (possession + biometric/PIN).
- Password sign-in is unchanged and still MFA-enforced. Entering a password only ever creates a pending login; a second factor (passkey, authenticator app, or a one-time recovery code) is mandatory before a session is issued, and accounts with no factor are still forced through enrollment first.
- New passkeys are discoverable by default (resident keys required), which is what enables one-tap sign-in. Existing passkeys keep working as a normal second factor; re-add one from Profile if it was registered before this release and you want it to work passwordless.
- Capability-gated, never blocking. The passkey button is hidden on IP-only installs (WebAuthn needs a domain) and on browsers without WebAuthn support; the password form always stays available. Cancel/timeout shows a short hint; rate-limited attempts reuse the existing lockout countdown.
Security
- Passwordless assertions require user verification and are bound to an HttpOnly ceremony cookie plus a single-use, 5-minute challenge row claimed atomically.
- The account is resolved from the assertion's WebAuthn user handle (
webauthn_users), never from request input; unknown/disabled/invalid all return the same generic 401 (no enumeration). - IP/account lockout counts failed passwordless attempts and resets only after a completed login; audit event
mfa.login_passkeyrecords{"passwordless":true}. - Sessions are minted only through the shared
mintLoginSessionchokepoint — the same path used by MFA and enrollment.
Upgrade notes
- No manual database steps. Migration 029 (nullable passwordless challenges) is additive and idempotent; the API applies it on boot and the normal one-line installer update picks it up.
- Existing passkeys from v1.1.0 were registered without the resident-key requirement and may not be discoverable. The password + MFA path is unaffected; add a fresh passkey from Profile → Add passkey to enable passwordless sign-in.
- IP-only deployments are unchanged: no passkey button, authenticator-app MFA continues to work.
Verification
- Backend: build + vet clean; unit suites green; full e2e against PostgreSQL 18 in 69.8 s — including 5 new passwordless suites (positive flow, password still
pending_mfa,residentKey=required, all 401 negatives — missing cookie / replayed challenge / unknown handle / wrong origin / disabled — and IP lockout). - Frontend: 33 files / 254 tests green,
tsc+ production build clean. - Migration 029 re-applied cleanly on an existing database (idempotency verified).
- Browser demo (real Chrome + CDP virtual authenticator): 7/7 flows, zero console errors — passkey button visible, forced enrollment, password still asks for MFA, then passwordless sign-in to the dashboard.