Passkey (WebAuthn) sign-in for accounts #334

Closed
opened 2026-11-09 13:54:03 +00:00 by jcoffey-dev · 3 comments
Owner

Requested on the forum (t/242). Users want to sign in with passkeys directly against their mail account, for example a password-manager passkey for daily use and a hardware key as a backup, without running an external identity provider.

Our own implementation (no upstream code). Planned for the series after 27.1; spec first.

Scope:

  • Credential. Passkeys stored on the account alongside the password. Multiple per account, each with a name, created and last-used times. Discoverable (resident) credentials with user verification required.
  • Management. Register, list, rename and remove passkeys through JMAP, with pages in the console (admin and self-service) and in webmail account settings. An admin can remove a user's passkeys for recovery.
  • Sign-in. Passkeys on the built-in login page, for the OAuth authorization-code and device flows. Browser conditional UI (autofill) where supported.
  • Policy. A per-domain or per-role setting to allow passkeys, and later to require them for browser sign-in.
  • Limits. Passkeys only cover browser and OAuth sign-in. IMAP, SMTP and other password-based protocols still use passwords or app passwords; the docs should say so.
  • Audit. Registration, removal and sign-in events in the audit log.

Notes: webauthn-rs (MPL-2.0) handles the protocol. The relying-party id comes from the server's public hostname, so changing it invalidates registered passkeys; the spec needs to cover that.

Requested on the forum (t/242). Users want to sign in with passkeys directly against their mail account, for example a password-manager passkey for daily use and a hardware key as a backup, without running an external identity provider. Our own implementation (no upstream code). Planned for the series after 27.1; spec first. Scope: - **Credential.** Passkeys stored on the account alongside the password. Multiple per account, each with a name, created and last-used times. Discoverable (resident) credentials with user verification required. - **Management.** Register, list, rename and remove passkeys through JMAP, with pages in the console (admin and self-service) and in webmail account settings. An admin can remove a user's passkeys for recovery. - **Sign-in.** Passkeys on the built-in login page, for the OAuth authorization-code and device flows. Browser conditional UI (autofill) where supported. - **Policy.** A per-domain or per-role setting to allow passkeys, and later to require them for browser sign-in. - **Limits.** Passkeys only cover browser and OAuth sign-in. IMAP, SMTP and other password-based protocols still use passwords or app passwords; the docs should say so. - **Audit.** Registration, removal and sign-in events in the audit log. Notes: `webauthn-rs` (MPL-2.0) handles the protocol. The relying-party id comes from the server's public hostname, so changing it invalidates registered passkeys; the spec needs to cover that.
jcoffey-dev added the
priority
p3
enhancement
labels 2026-11-09 13:54:03 +00:00
jcoffey-dev self-assigned this 2026-11-09 13:54:17 +00:00
jcoffey-dev added this to the 27.7 milestone 2026-11-16 15:22:42 +00:00
jcoffey-dev referenced this issue from a commit 2026-11-19 02:05:09 +00:00
Author
Owner

Server side of passkeys is in main (spec: docs/spec/features/passkeys.md, approved 2026-11-18):

  • #466 spec
  • #468 storage + inbuxa:Passkey/get and /set (create starts a registration and returns registrationUrl; rename; remove ends the account's sessions), sysPasskey* permissions
  • #469 registration page /passkey/register (password + TOTP, or an existing passkey, before the browser dialog), webauthn-rs 0.6.2
  • #470 sign-in in the authorization-code flow: autofill + "Sign in with a passkey" on the login page, POST /api/auth/passkey challenge, no TOTP after a passkey, counter check, audit via: passkey
  • #471 device flow, settings (passkeysAllowed / passkeyRpId / maxPasskeys on x:Authentication; passkeysAllowed off switches on x:Domain and x:Tenant), no passkeys on external directories, auth.passkey-counter event

Keeping this open for the pages:

  • Console: inbuxa: objects aren't in the schema, so it needs its own passkeys panel on the account (list with name/state/usable/backedUp/createdAt/lastUsedAt, rename, remove; an admin can't add one for someone). The settings already show on the Authentication, Domain and Tenant forms from the schema; passkeyRpId refusals come back as invalidProperties.
  • Webmail: Settings › Security › Passkeys, shown only when sign-in is OAuth: list, rename, remove (warn that removing signs out every session), and "Add a passkey", which calls inbuxa:Passkey/set create and opens registrationUrl in a new window (ticket good 10 minutes, shown once), then refreshes the list when the window closes. forbidden on create means passkeys are off for the account; overQuota means the limit is reached.
Server side of passkeys is in `main` (spec: `docs/spec/features/passkeys.md`, approved 2026-11-18): - #466 spec - #468 storage + `inbuxa:Passkey/get` and `/set` (create starts a registration and returns `registrationUrl`; rename; remove ends the account's sessions), `sysPasskey*` permissions - #469 registration page `/passkey/register` (password + TOTP, or an existing passkey, before the browser dialog), webauthn-rs 0.6.2 - #470 sign-in in the authorization-code flow: autofill + "Sign in with a passkey" on the login page, `POST /api/auth/passkey` challenge, no TOTP after a passkey, counter check, audit `via: passkey` - #471 device flow, settings (`passkeysAllowed` / `passkeyRpId` / `maxPasskeys` on x:Authentication; `passkeysAllowed` off switches on x:Domain and x:Tenant), no passkeys on external directories, `auth.passkey-counter` event Keeping this open for the pages: - **Console:** `inbuxa:` objects aren't in the schema, so it needs its own passkeys panel on the account (list with name/state/usable/backedUp/createdAt/lastUsedAt, rename, remove; an admin can't add one for someone). The settings already show on the Authentication, Domain and Tenant forms from the schema; `passkeyRpId` refusals come back as `invalidProperties`. - **Webmail:** Settings › Security › Passkeys, shown only when sign-in is OAuth: list, rename, remove (warn that removing signs out every session), and "Add a passkey", which calls `inbuxa:Passkey/set` create and opens `registrationUrl` in a new window (ticket good 10 minutes, shown once), then refreshes the list when the window closes. `forbidden` on create means passkeys are off for the account; `overQuota` means the limit is reached.
Author
Owner

Passkeys are done across the suite:

  • Server: spec #466; storage and inbuxa:Passkey management #468; the registration page on the mail host #469; sign-in on the login page with autofill and a "Sign in with a passkey" button #470; the device flow, the on/off switches (server, tenant, domain) and audit #471.
  • Console: inbuxa/inbuxa-admin#247, a passkeys panel on a person's account page.
  • Webmail: inbuxa/inbuxa-webmail#116, Settings › Security › Passkeys: list, rename, remove, and add (opens the server's registration page). Shown when sign-in goes through the mail server's page.

Passkeys cover browser and OAuth sign-in only; mail apps keep using passwords or app passwords. It ships in the next RCs of the server, console and webmail. Thanks to @StefanSa for asking in t/242.

Passkeys are done across the suite: - **Server:** spec #466; storage and `inbuxa:Passkey` management #468; the registration page on the mail host #469; sign-in on the login page with autofill and a "Sign in with a passkey" button #470; the device flow, the on/off switches (server, tenant, domain) and audit #471. - **Console:** inbuxa/inbuxa-admin#247, a passkeys panel on a person's account page. - **Webmail:** inbuxa/inbuxa-webmail#116, Settings › Security › Passkeys: list, rename, remove, and add (opens the server's registration page). Shown when sign-in goes through the mail server's page. Passkeys cover browser and OAuth sign-in only; mail apps keep using passwords or app passwords. It ships in the next RCs of the server, console and webmail. Thanks to @StefanSa for asking in t/242.
Author
Owner

Follow-up from the end-to-end check: with passkeys off for an account, the webmail and console offered "Add a passkey" and only said no after the click. The session now says up front whether adding is allowed and the account's limit (#474, spec PK-19), and the webmail (inbuxa/inbuxa-webmail#117) and console (inbuxa/inbuxa-admin#248) show the note instead of the add form. In the next RCs.

Follow-up from the end-to-end check: with passkeys off for an account, the webmail and console offered "Add a passkey" and only said no after the click. The session now says up front whether adding is allowed and the account's limit (#474, spec PK-19), and the webmail (inbuxa/inbuxa-webmail#117) and console (inbuxa/inbuxa-admin#248) show the note instead of the add form. In the next RCs.
jcoffey-dev modified the milestone from 27.7 to 27.1 2026-11-19 16:29:46 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: inbuxa/inbuxa-server#334