Part of #334: the console side of passkeys, on top of inbuxa-server #468 to #471.
A person's account page gets a Passkeys card under the form:
Lists the account's passkeys (inbuxa:Passkey/get with the account's own accountId): name, added, last used, and marks for synced, needs re-adding (registered for the server's earlier name) and not finished (pending).
An administrator can rename and remove them, and remove all for recovery. The dialog says removing one signs the account out everywhere and that the password still works.
On the admin's own account, Add a passkey creates one and opens the returned registrationUrl in a new window, then refreshes the list when it closes. If the browser blocks the window, the one-time link (10 minutes) is shown instead. forbidden (passkeys off) and overQuota get their own messages.
Gated on sysPasskeyGet/Update/Destroy/Create, plus sysAccountUpdate for someone else's account. On an older server, or an account out of reach, the card doesn't show.
The passkey settings themselves already appear on the Authentication, Domain and Tenant forms through the schema.
Checks run locally: typecheck, lint, i18n:check, tests (1146, new passkeys.test.ts), the three shell tests, build, notice-check.
Part of #334: the console side of passkeys, on top of inbuxa-server #468 to #471.
A person's account page gets a **Passkeys** card under the form:
- Lists the account's passkeys (`inbuxa:Passkey/get` with the account's own `accountId`): name, added, last used, and marks for synced, needs re-adding (registered for the server's earlier name) and not finished (pending).
- An administrator can rename and remove them, and remove all for recovery. The dialog says removing one signs the account out everywhere and that the password still works.
- On the admin's own account, **Add a passkey** creates one and opens the returned `registrationUrl` in a new window, then refreshes the list when it closes. If the browser blocks the window, the one-time link (10 minutes) is shown instead. `forbidden` (passkeys off) and `overQuota` get their own messages.
- Gated on `sysPasskeyGet`/`Update`/`Destroy`/`Create`, plus `sysAccountUpdate` for someone else's account. On an older server, or an account out of reach, the card doesn't show.
The passkey settings themselves already appear on the Authentication, Domain and Tenant forms through the schema.
Checks run locally: typecheck, lint, i18n:check, tests (1146, new `passkeys.test.ts`), the three shell tests, build, notice-check.
Lists the account's passkeys (inbuxa:Passkey/get): name, added, last
used, synced, needs re-adding, not finished. An administrator can
rename and remove them, or remove all for recovery; the dialog says
removing one signs the account out everywhere. On the admin's own
account, Add a passkey creates one and opens the server's registration
page in a new window, refreshing the list when it closes; a blocked
window shows the one-time link instead. Passkeys turned off and a full
account get their own messages. Gated on the sysPasskey* permissions,
plus account update for someone else's account; an older server shows
nothing.
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: the console side of passkeys, on top of inbuxa-server #468 to #471.
A person's account page gets a Passkeys card under the form:
inbuxa:Passkey/getwith the account's ownaccountId): name, added, last used, and marks for synced, needs re-adding (registered for the server's earlier name) and not finished (pending).registrationUrlin a new window, then refreshes the list when it closes. If the browser blocks the window, the one-time link (10 minutes) is shown instead.forbidden(passkeys off) andoverQuotaget their own messages.sysPasskeyGet/Update/Destroy/Create, plussysAccountUpdatefor someone else's account. On an older server, or an account out of reach, the card doesn't show.The passkey settings themselves already appear on the Authentication, Domain and Tenant forms through the schema.
Checks run locally: typecheck, lint, i18n:check, tests (1146, new
passkeys.test.ts), the three shell tests, build, notice-check.