Passkeys: review fixes for locking, challenges and confirmation forms
- github
- github/openchronology/timeline-app
- commit
- main
- github/athanclark
- Passwordless sign-in locks the account, then re-reads the passkey under the lock, refusing one removed meanwhile and checking the latest counter. - Challenges are used up on a small pool of their own, so concurrent confirmations cannot exhaust the main pool; expired ones are swept outside any transaction. - Finishing an enrollment no longer re-requires a five-minute-old sign-in for accounts without a password; the options step checked it. - A browser already signed in may sign in with a passkey (bound to its session), as with a password. - /api/session says whether a pending two-factor step can take a passkey; the sign-in page offers it only then. - AccountSecurity.endAccess and setRecoveryCodes replace the repeated revocation and recovery-code code, and clear passkey challenges too. - The confirmation fields drop a spent passkey answer after each submit and take the CSRF token as a prop; /admin asks for a passkey only when the administrator has one. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/openchronology/timeline-app/commit/899a3261b04638a81a6f5ad8d9d54dfc33853370
Open Passkeys: review fixes for locking, challenges and confirmation forms in the timeline