Passkeys: storage and inbuxa:Passkey management (#334) #468

Merged
jcoffey-dev merged 1 commits from feat/334-passkey-storage into main 2026-11-19 03:12:20 +00:00
1 Commits
Author SHA1 Message Date
jcoffey-dev dd2e605e88 Passkeys: storage and inbuxa:Passkey management (#334)
ci / fork-checks (pull_request) Skipped
ci / build (pull_request) Skipped
github/ci (branch) GitHub Actions
ci / github (pull_request) Successful in 14m7s
First part of passkeys (docs/spec/features/passkeys.md). An account's
passkeys are kept in the fork's own data under N, apart from the
account's credentials, so a server that doesn't know passkeys still
reads every account.

inbuxa:Passkey/get lists an account's passkeys; the request's accountId
names the account. /set create starts a registration: a pending passkey
and the registration page's URL, with a ticket good for 10 minutes and
returned once. An account has at most 10, pending ones included. Update
changes the name only. Destroy removes one; removing a registered one
moves the account's credential version, so every session ends, as after
a password change. Deleting an account removes its passkeys.

People manage their own with the new sysPasskeyGet, sysPasskeyCreate,
sysPasskeyUpdate and sysPasskeyDestroy permissions, granted to users,
tenant administrators and server administrators by default. Reaching
another account's passkeys also takes sysAccountUpdate, an account in
reach, and no permission on it the caller lacks. Every change is in the
audit log, named by the passkey's name.

The registration page (PK-6), sign-in and the settings follow in their
own PRs. The spec now has the page ask for the password or an existing
passkey before it registers a new one (PK-8), and notes that the
console needs its own passkeys panel.
2026-11-18 19:57:46 -07:00