#372 Passkeys (WebAuthn) for two-factor and sign-in
–
- github
- github/openchronology/timeline-app
- github/openchronology/timeline-app#372
- issue
- state:closed
Two-factor authentication today is TOTP (an authenticator app's six-digit codes, `docs/authentication.md`), which the docs note "is not phishing resistant. Passkeys/WebAuthn would be a stronger future option." **Proposal:** support passkeys (WebAuthn) as a second factor and, optionally, as a sign-in method of their own. - **Enroll and manage** under **Account → Account security**: register one or more passkeys with a name, list them with when each was added and last used, and remove one (with the same re-authentication as other security changes; enrolling and removing revoke other sessions and send a notification, as TOTP does). - **As a second factor:** after a password or social sign-in, an account with a passkey can answer the challenge with it instead of a TOTP code; recovery codes keep working. - **Passwordless sign-in (optional, behind a setting):** "Sign in with a passkey" on the sign-in page using discoverable credentials. - **Server:** store each credential's ID, public key, sign count, transports and AAGUID per account (schema migration); verify registration and assertion server-side (origin and RP ID from the site's configured address; user verification required); reject cloned credentials by sign count where authenticators report one. - **Desktop:** desktop sign-in already goes through the system browser, so it works there unchanged. - **Admin:** account security changes and moderation decisions accept a passkey where they accept a TOTP code today. - **Docs and tests:** `docs/authentication.md`, the FAQ, and browser tests with Playwright's virtual authenticator (CDP `WebAuthn.addVirtualAuthenticator` in Chromium). https://github.com/openchronology/timeline-app/issues/372
Related
Open #372 Passkeys (WebAuthn) for two-factor and sign-in in the timeline