Stalwart 1.1.0: passkeys, and the role permissions an upgrade leaves out
Stalwart 1.1.0 came out on November 9, 2026. The vendor leads with passkeys as a new way to sign in, but the line that matters to an admin sits at the very top of the release notes and is easy to skim past. We checked what applies to us. The measurement date is November 15, 2026.
What is new
Passkeys (WebAuthn) are available for accounts in the internal directory. You sign in on the built-in login page without a password, via a button or browser autofill. ES256, Ed25519 and RS256 keys are supported, and each account may hold ten passkeys by default. The relying party ID is the host of the public URL, so the WebUI has to run on that host or one of its subdomains. (Vendor claim, release notes.)
Here a passkey is not a second factor. Signing in with one does not prompt for the TOTP code. Registering a passkey takes the current password and, if set, the TOTP code.
The upgrade trap
Managing passkeys requires new sysPasskey permissions. Default roles created by an older version do not include them. There are two ways to fix that:
- Add the permissions by hand using the recovery administrator.
- Start the server once with the environment variable
STALWART_UPDATE_ROLE_PERMISSIONS=true, then remove the variable.
The procedure is documented under "Default roles on upgraded servers". If the permissions are missing, accounts on the default roles cannot use the feature, and the WebUI does not show it to them (documentation). Remove the variable after the restart: while it is set, every start adds back permissions that someone removed from a default role on purpose, unless they are listed in the role's disabledPermissions. The server logs each role it changes. In a cluster, set the variable on one node only. (All per the documentation, read on 15 November 2026.)
Passkeys aside, 1.1.0 fixes things that matter in daily operation. On shutdown the server now drains in-flight outbound deliveries for up to eight seconds, so a restart no longer causes duplicate deliveries. Milter header edits now follow libmilter, and a fresh install with an external directory gets the default roles so directory users can log in.
What we run
The homelab mail host runs the stalwartlabs/stalwart container at version 1.0.2 (image of November 2, 2026, started the same day; measured on November 15, 2026 with docker logs and docker exec stalwart stalwart --version, read-only). We skipped 1.0.3 of November 4, and 1.1.0 is not installed.
We did not read which directories authenticate our accounts out of the server configuration. Whether our accounts authenticate internally or against an external directory is open. For any account that authenticates against an external directory the passkey feature does nothing, because the release notes limit it to the internal directory. The delivery fixes would then be the reason to update, not the headline.
What to do as an admin
- Read the running version with
docker exec <container> stalwart --version; the image tag may differ. - Find out which directory authenticates your accounts. Only internal accounts get passkeys.
- Upgrade a copy and start it once with
STALWART_UPDATE_ROLE_PERMISSIONS=true. Then remove the variable, restart, and register a test passkey. - Only then go to production. The way back is the old image plus the backed-up data directory.
If you are coming from the 0.x line, the migration pitfalls are in our posts Stalwart 1.0: mandatory migration, not an upgrade and the migration guide. Mail and server operations belong to our topic area Servers and network, and if you would rather not run mail infrastructure alone, our IT infrastructure and operations service is the place to start.
Open points: We did not check which directory our accounts actually authenticate against, nor whether 1.1.0 runs cleanly for us; it is not installed. Whether missing permissions produce an error message or only a missing feature is not stated by the documentation (it says: not shown).
Read next: the Exchange Online outage of 12 and 13 November · the PostgreSQL 14 fleet check across 14 databases · Synology C2 Identity Edge Server and its CVSS discrepancy · Stalwart, Axigen and Exchange compared
Further Reading
How we measured our own values: read-only SSH to the mail host on 15 November 2026 around 16:55 CET: docker ps, docker inspect stalwart (image and start time), docker exec stalwart stalwart --version returns 1.0.2.
- Stalwart Labs, release notes 1.1.0 of November 9, 2026, primary source, verified (the release list also confirms 1.0.3 of November 4 and 1.0.2 of November 2)
- Stalwart, permissions documentation, section Default roles on upgraded servers, vendor documentation, verified
Do I have to add anything by hand for Stalwart 1.1.0?+
Yes, if the installation predates it. Passkey management needs new sysPasskey permissions that the default roles of earlier versions do not contain. Either add them with the recovery administrator, or start the server once with STALWART_UPDATE_ROLE_PERMISSIONS=true and remove the variable afterwards.
Do passkeys work for accounts that authenticate against LDAP or Active Directory?+
According to the release notes, only for accounts in the internal directory. If you run Stalwart against an external directory, those accounts do not get the feature. The permissions question on upgrade still applies, because it concerns the default roles.
Does a passkey replace the second factor?+
No, it replaces the password. The release notes say outright that a passkey is not a second factor: signing in with one does not ask for a TOTP code. Registering one, on the other hand, requires the current password and the TOTP code if one is set.
senn-tech