Passkeys: the registration page (#334) #469

Merged
jcoffey-dev merged 1 commits from feat/334-passkey-register into main 2026-11-19 03:27:22 +00:00
1 Commits
Author SHA1 Message Date
jcoffey-dev 138178c85b Passkeys: the registration page (#334)
ci / fork-checks (pull_request) Skipped
ci / build (pull_request) Skipped
github/ci (branch) GitHub Actions
ci / github (pull_request) Successful in 12m46s
Second part of passkeys (docs/spec/features/passkeys.md, PK-6 to PK-8).
The server now serves /passkey/register, the page an inbuxa:Passkey
create's registrationUrl opens, next to the login page.

The page asks for the account's password, and its TOTP code when it has
one, before the browser's passkey dialog: a stolen session token can
start a registration but not finish one. It posts to
/api/passkey/register in two steps. "start" checks the ticket and the
password through the usual sign-in path (limits and failure counting
included) and answers with the WebAuthn options: a discoverable
credential, user verification required, attestation none, the account's
existing passkeys excluded. "finish" checks what the browser made and
turns the passkey active. What "start" began waits in the in-memory
store, so any node can finish it, and is good once.

The relying-party id is the host of the server's public URL, and that
URL is the only origin accepted. A credential id already registered to
any account is refused. Each account gets a random user handle the
first time it registers one, for sign-in to find it by.

The WebAuthn checks come from webauthn-rs 0.6.2 (MPL-2.0; its new
dependencies are MIT or Apache-2.0, crypto-glue MPL-2.0; no OpenSSL).
It tests ES256, ES384 and RS256, so the spec's algorithm list now says
those.

The "or an active passkey" of PK-8 arrives with passkey sign-in.
2026-11-18 20:13:31 -07:00