Part of inbuxa/inbuxa-server#334 (the server side is in inbuxa-server #466, #468-#471).
Settings › Security gets a Passkeys section when sign-in goes through the mail server's page (signIn: oauth), the only place a passkey can be used. A server without inbuxa:Passkey hides it.
Lists the account's passkeys: name, added, last used, with "synced" (backed up), "needs re-adding" (registered for the server's old name, PK-4) or "not finished" (pending).
Rename (active ones) and remove. Removing one ends every session of the account (PK-15), so after it the webmail signs out and the sign-in page says the sign-in ended.
Add a passkey creates a pending record with inbuxa:Passkey/set and opens the returned registrationUrl on the mail server in a new window (opened on the click, so it isn't blocked as a pop-up; same tab if the browser refuses). The list refreshes when that window closes.
Refusals: forbidden says passkeys are off for this account, overQuota says the account is at its limit.
New strings in all ten catalogs, AI-written and not reviewed by native speakers.
Checks run locally: typecheck, web tests (1607, 5 new for lib/passkeys), server tests (316), release-version.test.sh, build, i18n check (1760/1760 everywhere). Not tried against a live server yet.
Part of inbuxa/inbuxa-server#334 (the server side is in inbuxa-server #466, #468-#471).
Settings › Security gets a **Passkeys** section when sign-in goes through the mail server's page (`signIn: oauth`), the only place a passkey can be used. A server without `inbuxa:Passkey` hides it.
- Lists the account's passkeys: name, added, last used, with "synced" (backed up), "needs re-adding" (registered for the server's old name, PK-4) or "not finished" (pending).
- Rename (active ones) and remove. Removing one ends every session of the account (PK-15), so after it the webmail signs out and the sign-in page says the sign-in ended.
- **Add a passkey** creates a pending record with `inbuxa:Passkey/set` and opens the returned `registrationUrl` on the mail server in a new window (opened on the click, so it isn't blocked as a pop-up; same tab if the browser refuses). The list refreshes when that window closes.
- Refusals: `forbidden` says passkeys are off for this account, `overQuota` says the account is at its limit.
- New strings in all ten catalogs, AI-written and not reviewed by native speakers.
Checks run locally: typecheck, web tests (1607, 5 new for `lib/passkeys`), server tests (316), `release-version.test.sh`, build, i18n check (1760/1760 everywhere). Not tried against a live server yet.
With sign-in on the mail server's page, Security lists the account's
passkeys (inbuxa:Passkey): name, added, last used, and "synced",
"needs re-adding" or "not finished". Rename and remove them; removing
one ends every session, so the webmail signs out with a note. "Add a
passkey" creates a pending one and opens its registration page on the
mail server in a new window, then refreshes the list when that window
closes. A server without passkeys hides the section. New strings in all
ten catalogs, AI-written and not yet reviewed.
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 inbuxa/inbuxa-server#334 (the server side is in inbuxa-server #466, #468-#471).
Settings › Security gets a Passkeys section when sign-in goes through the mail server's page (
signIn: oauth), the only place a passkey can be used. A server withoutinbuxa:Passkeyhides it.inbuxa:Passkey/setand opens the returnedregistrationUrlon the mail server in a new window (opened on the click, so it isn't blocked as a pop-up; same tab if the browser refuses). The list refreshes when that window closes.forbiddensays passkeys are off for this account,overQuotasays the account is at its limit.Checks run locally: typecheck, web tests (1607, 5 new for
lib/passkeys), server tests (316),release-version.test.sh, build, i18n check (1760/1760 everywhere). Not tried against a live server yet.