Linus Rath 5597eadc28 fix: give a server its own sign-in button only when it has a button label #1135 ...

A server entry's OAuth client ID already has a meaning while OAuth is
off globally: it is the registered client that password and TOTP logins
use with Stalwart's require_client_registration. The PR made every such
entry offer OAuth on its own, so existing installs would suddenly run
discovery and show SSO buttons on the login page, and multi-IdP setups
would get one extra button per server.

A server now gets its own button only with both a client ID and a button
label, which no existing config has. The rule lives in `offersOwnOAuth`
with a test. Also:
- the OAuth-only login form uses the selected server's label
- the public config validator checks `buttonLabel` is a string
- the admin hint and `.env.example` say the label enables the button

2026-10-01 11:01:17 +02:00

..

jmap-servers-oauth-label.test.ts

fix: give a server its own sign-in button only when it has a button label #1135

2026-10-01 11:01:17 +02:00

migrate-policy.test.ts

feat(unified-mailbox): account-bounded Unified Mailbox with opt-in cross-account

2026-07-11 21:14:34 +02:00

plugin-signing.test.ts

fix: treat an empty PLUGIN_SIGNING_KEY_FILE as unset #996

2026-09-30 14:24:29 +02:00