Part of #334. Step 1 of 4 in docs/spec/features/passkeys.md.
Passkeys kept in the fork's own data (_, prefix N, claimed in the layout's owner table), apart from account credentials.
inbuxa:Passkey/get and /set: create starts a registration (a pending passkey plus the registration page URL, ticket good 10 minutes, shown once); rename; remove. At most 10 per account.
Removing a registered passkey moves the account's credential version, so every session ends (PK-15). Deleting an account removes its passkeys (PK-16).
New permissions sysPasskeyGet/Create/Update/Destroy (698-701), default for users, tenant admins and server admins. Another account's passkeys also need sysAccountUpdate, reach, and no permission the caller lacks.
Audited by the existing set layer; privacy catalog entry added.
Tests: unit tests for keys, names, ids, expiry and the credential version; system test system::passkeys::passkey_tests (create, validation, rename, the limit, another user refused, admin removal, audit) passes locally. fmt, fork checks, privacy check, expr-schema.py --check and cargo test --workspace --locked --no-run are clean.
Part of #334. Step 1 of 4 in `docs/spec/features/passkeys.md`.
- Passkeys kept in the fork's own data (`_`, prefix `N`, claimed in the layout's owner table), apart from account credentials.
- `inbuxa:Passkey/get` and `/set`: create starts a registration (a pending passkey plus the registration page URL, ticket good 10 minutes, shown once); rename; remove. At most 10 per account.
- Removing a registered passkey moves the account's credential version, so every session ends (PK-15). Deleting an account removes its passkeys (PK-16).
- New permissions `sysPasskeyGet/Create/Update/Destroy` (698-701), default for users, tenant admins and server admins. Another account's passkeys also need `sysAccountUpdate`, reach, and no permission the caller lacks.
- Audited by the existing set layer; privacy catalog entry added.
Tests: unit tests for keys, names, ids, expiry and the credential version; system test `system::passkeys::passkey_tests` (create, validation, rename, the limit, another user refused, admin removal, audit) passes locally. fmt, fork checks, privacy check, `expr-schema.py --check` and `cargo test --workspace --locked --no-run` are clean.
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Part of #334. Step 1 of 4 in
docs/spec/features/passkeys.md._, prefixN, claimed in the layout's owner table), apart from account credentials.inbuxa:Passkey/getand/set: create starts a registration (a pending passkey plus the registration page URL, ticket good 10 minutes, shown once); rename; remove. At most 10 per account.sysPasskeyGet/Create/Update/Destroy(698-701), default for users, tenant admins and server admins. Another account's passkeys also needsysAccountUpdate, reach, and no permission the caller lacks.Tests: unit tests for keys, names, ids, expiry and the credential version; system test
system::passkeys::passkey_tests(create, validation, rename, the limit, another user refused, admin removal, audit) passes locally. fmt, fork checks, privacy check,expr-schema.py --checkandcargo test --workspace --locked --no-runare clean.