# grommunio native clients after Keycloak SSO: Thunderbird, Outlook, EWS, EAS and MFA explained

Source: https://forgeone.solutions/en/tech/grommunio-native-clients-after-keycloak-sso
Language: en
Published: 2026-10-03
Updated: 2026-11-17

Practical acceptance guide for Thunderbird, AutoConfig, AutoDiscover, EWS, EAS, Outlook boundaries and MFA after upgrading to grommunio 2026.06.2.

## Why this test matters after the SSO upgrade

Part 15 covered the upgrade from grommunio 2026.06.1 to 2026.06.2 with Keycloak SSO, MFA, AutoDiscover and mailflow acceptance. This article continues from there: what does central login mean for native clients such as Thunderbird, Outlook, EWS and ActiveSync? The upgrade guide is linked here: [grommunio 2026.06.2 upgrade and technical acceptance](https://forgeone.solutions/en/tech/grommunio-2026-06-2-upgrade-keycloak-sso-practice).

The most important lesson is simple: browser SSO and native mail protocols are different acceptance areas. Keycloak can centralize web logins and OIDC-capable applications, but IMAP, SMTP, EWS, CalDAV, CardDAV and EAS still need separate testing after an upgrade. A successful web login does not replace native client acceptance.

## Overview

Thunderbird was tested with a fresh profile against the upgraded appliance. AutoConfig, AutoDiscover V1/V2, IMAP, SMTP, EWS and ActiveSync were technically validated. CalDAV and CardDAV were checked for DAV reachability, not full calendar and contacts CRUD. Outlook was deliberately not marked PASS without a real GUI/MAPI acceptance run.

MFA is classified for browser SSO and is not applied generically to native protocols. This distinction matters for customers running grommunio with Keycloak in production.

[![Thunderbird with a grommunio IMAP account after upgrading to grommunio 2026.06.2](https://forgeone.solutions/media/06-thunderbird-156-current-inbox.png)](https://forgeone.solutions/media/06-thunderbird-156-current-inbox.png)

Screenshot: Thunderbird 156.0 with a fresh profile and a grommunio IMAP account after the upgrade. The UI was captured in an isolated GUI test environment; the acceptance covered profile, login, Inbox, IMAP, SMTP and mailflow.

## Lab baseline

| Area | Value | Classification |
| --- | --- | --- |
| Appliance | grommunio 2026.06.2 on openSUSE Leap 16.0 | Target state after upgrading from 2026.06.1 |
| System status | No failed systemd units, no reboot required according to zypper ps -s | Clean operational starting point |
| Users | alice@example.test and bob@example.test | Separate test accounts for client and mailflow checks |
| Client | Thunderbird 156.0 with isolated profile | No legacy state from existing profiles |
| SSO context | Keycloak/OIDC browser flows already accepted in part 15 | Native protocols checked separately |

## Thunderbird AutoConfig

Thunderbird should not rely on guessed manual server entries where AutoConfig can provide correct settings. The known AutoConfig paths were checked with Host/SNI set to mail.example.test. Both relevant paths returned XML and were usable for account configuration.

```text
/.well-known/autoconfig/mail/config-v1.1.xml
/mail/config-v1.1.xml
```

In a customer environment, repeat the same check with the real mail FQDN, a valid TLS certificate and externally resolvable DNS. The response should not only return HTTP 200; it should contain the expected IMAP/SMTP hosts and ports.

```bash
curl -fsS https://mail.example.test/.well-known/autoconfig/mail/config-v1.1.xml
curl -fsS https://mail.example.test/mail/config-v1.1.xml
```

## Actually test IMAP and SMTP

For users, the relevant question is not whether a port is open. The client must authenticate, read folders, send mail and show delivery. The lab therefore checked IMAP folder listing, SMTP Submission with STARTTLS/AUTH and mailflow from Alice to Bob. A message with an attachment was also created.

```bash
openssl s_client -starttls imap -connect mail.example.test:143 -servername mail.example.test
openssl s_client -starttls smtp -connect mail.example.test:587 -servername mail.example.test
```

| Check | Expectation | Result |
| --- | --- | --- |
| IMAP login | Client authenticates and reads folders | PASS |
| SMTP Submission | STARTTLS and SMTP AUTH accept the user | PASS |
| Mailflow Alice to Bob | Message is delivered and found through IMAP | PASS |
| Attachment | Message with attachment is accepted and delivered | PASS |
| Reply in GUI client | Reply is created and delivered in the client | NOT TESTED |
| Sent Items in GUI client | Sent message appears in Sent Items | PARTIAL |

## AutoDiscover, EWS and Outlook

AutoDiscover is critical for Exchange-like clients. V1 and V2 were technically checked. EWS was validated with a SOAP GetFolder test. That is strong protocol evidence, but it does not replace a real Outlook GUI or MAPI test. Outlook therefore remains NOT TESTED in this acceptance run.

The practical distinction is important: AutoDiscover can answer correctly while a specific client still fails later because of profile state, certificates, authentication mode or policies. AutoDiscover, EWS and a real client test should therefore be documented separately.

| Check | Test | Result |
| --- | --- | --- |
| AutoDiscover V1 | POST to /Autodiscover/Autodiscover.xml | PASS |
| AutoDiscover V2 EWS | JSON discovery for alice@example.test with Protocol=EWS | PASS |
| EWS | SOAP GetFolder against msgfolderroot | PASS |
| Outlook GUI / MAPI | Real Outlook profile with mailflow and calendar | NOT TESTED |

## ActiveSync and mobile clients

ActiveSync was checked as a protocol path with a controlled client. For production acceptance, a real iOS or Android device should additionally be tested against the customer policy set. The MDM part of the series remains relevant here: [grommunio MDM 2026 step by step](https://forgeone.solutions/en/tech/grommunio-mdm-2026-step-by-step).

```bash
curl -I https://mail.example.test/Microsoft-Server-ActiveSync
```

| Check | Test | Result |
| --- | --- | --- |
| EAS challenge | Microsoft-Server-ActiveSync returns expected auth challenge | PASS |
| EAS controlled client | FolderSync/protocol path technically checked | PASS WITH CONDITIONS |
| Real mobile device | iOS/Android with policy, sync and remote wipe | NOT TESTED |

## CalDAV and CardDAV

Calendars and contacts must not be inferred from mail tests. The lab checked DAV discovery and authenticated PROPFIND. That is enough to state that the DAV path is basically reachable. Full calendar and contacts CRUD in Thunderbird remains a separate client acceptance step.

## Where Keycloak actually applies

| Area | Typical authentication | MFA classification |
| --- | --- | --- |
| grommunio Web | Browser SSO through Keycloak/OIDC | MFA can apply in the browser flow |
| grommunio Admin | SSO/OIDC depending on configuration | MFA can apply in the browser flow |
| grommunio Files | OIDC/browser flow | MFA can apply in the browser flow |
| grommunio Chat | SSO mapping must be checked after migration | MFA can apply in the browser flow |
| Thunderbird IMAP/SMTP | Native protocol authentication | Not automatically identical to browser MFA |
| EWS | Exchange Web Services protocol authentication | Do not count as browser MFA |
| EAS | ActiveSync protocol authentication | Test device-specific behavior |
| Outlook/MAPI | Client and profile dependent | Do not claim without a real Outlook test |

## Technical acceptance

PASS means the specific check was executed and evidenced in the lab. PARTIAL and NOT TESTED remain visible so a successful browser SSO flow is not mistaken for full native client acceptance.

| Area | Check | Result |
| --- | --- | --- |
| Appliance health | Package state, zypper ps -s, systemctl --failed, services | PASS |
| Thunderbird profile | Fresh profile, IMAP account visible, Inbox screenshot | PASS |
| Thunderbird IMAP | Login, folder listing, Inbox visible | PASS |
| Thunderbird SMTP | STARTTLS/AUTH and delivery | PASS |
| Thunderbird attachment | Message with attachment created and delivered | PASS |
| AutoConfig | Thunderbird configuration XML through known paths | PASS |
| AutoDiscover V1 | XML AutoDiscover | PASS |
| AutoDiscover V2 | JSON discovery for EWS | PASS |
| EWS | SOAP GetFolder | PASS |
| EAS | Controlled protocol test | PASS WITH CONDITIONS |
| CalDAV/CardDAV | DAV discovery and authenticated PROPFIND | PARTIAL |
| Outlook GUI / MAPI | Real Outlook profile | NOT TESTED |
| MFA for native clients | Not inferred generically from browser SSO | PASS |

## Step-by-step acceptance after the upgrade

| Step | What to check | Why it matters |
| --- | --- | --- |
| 1 | Check appliance health, services and reboot need | Client errors must not come from a broken baseline |
| 2 | Test AutoConfig and AutoDiscover with the real hostname | Clients need working discovery |
| 3 | Configure Thunderbird with a fresh profile | Old profiles can hide configuration problems |
| 4 | Check IMAP, SMTP and mailflow with real test accounts | Web login alone proves no mailflow |
| 5 | Check EWS separately | Exchange-like clients depend on separate discovery and authentication |
| 6 | Retest EAS with a real device | Policies, sync and device behavior are production-relevant |
| 7 | Document the MFA matrix | Browser MFA must not be confused with native protocol auth |
| 8 | Record PASS, PARTIAL and NOT TESTED | Customers immediately see what was actually accepted |

## Minimum technician log

To keep acceptance reproducible, do not record the result only as free text. A compact log per client and protocol path works well: version, fresh or existing profile, FQDN used, TLS status, authentication mode, expected result, actual result and explicit classification.

| Field | Example | Why record it |
| --- | --- | --- |
| Client version | Thunderbird 156.0 | Screenshots alone do not reliably prove package version |
| Profile state | freshly created | Old profiles can distort successful tests |
| FQDN | mail.example.test | Discovery depends on hostname, SNI and certificate |
| Auth path | IMAP/SMTP Basic, browser SSO separate | Avoid mixing MFA and Keycloak claims incorrectly |
| Test data | Alice sends to Bob with attachment | Mailflow must be reproducible |
| Classification | PASS, PARTIAL or NOT TESTED | Open points remain visible |

## Conclusion

After upgrading to grommunio 2026.06.2, opening Web, Admin and Keycloak is not enough. Native clients must be accepted with their own protocols. Thunderbird, IMAP, SMTP, AutoConfig, AutoDiscover and EWS produced solid evidence in the lab. EAS is technically validated but still needs a real device scenario for customer acceptance. Outlook/MAPI deliberately remains open without a real Outlook test.

That clean separation makes the guide reproducible: central login improves browser and SSO operations, but every native protocol needs its own post-upgrade check.

## Hero image

[![Thunderbird with a grommunio IMAP account after upgrading to grommunio 2026.06.2](https://forgeone.solutions/media/06-thunderbird-156-current-inbox.png)](https://forgeone.solutions/media/06-thunderbird-156-current-inbox.png)

## Author

Mathias Rumbold

## Category

- [grommunio & Groupware](https://forgeone.solutions/en/tech/grommunio-native-clients-after-keycloak-sso?category=grommunio-groupware)

## Tags

- [grommunio](https://forgeone.solutions/en/tech/grommunio-native-clients-after-keycloak-sso?tags=grommunio)
- [Groupware](https://forgeone.solutions/en/tech/grommunio-native-clients-after-keycloak-sso?tags=groupware)
- [Collaboration](https://forgeone.solutions/en/tech/grommunio-native-clients-after-keycloak-sso?tags=collaboration)
- [Exchange alternative](https://forgeone.solutions/en/tech/grommunio-native-clients-after-keycloak-sso?tags=exchange-alternative)
- [Native Exchange Replacement](https://forgeone.solutions/en/tech/grommunio-native-clients-after-keycloak-sso?tags=native-exchange-replacement)
- [Security](https://forgeone.solutions/en/tech/grommunio-native-clients-after-keycloak-sso?tags=security)
- [Keycloak](https://forgeone.solutions/en/tech/grommunio-native-clients-after-keycloak-sso?tags=keycloak)
- [SSO](https://forgeone.solutions/en/tech/grommunio-native-clients-after-keycloak-sso?tags=sso)
- [MFA](https://forgeone.solutions/en/tech/grommunio-native-clients-after-keycloak-sso?tags=mfa)
- [Enterprise Linux](https://forgeone.solutions/en/tech/grommunio-native-clients-after-keycloak-sso?tags=enterprise-linux)
- [Upgrade](https://forgeone.solutions/en/tech/grommunio-native-clients-after-keycloak-sso?tags=upgrade)

## Validate your grommunio clients

ForgeOne supports grommunio upgrades, Keycloak SSO, client acceptance and production-ready operating procedures.

[Discuss a grommunio project](https://forgeone.solutions/en/contact)

## grommunio 2026 Schritt für Schritt

Die Beiträge bauen chronologisch aufeinander auf: Installation, Security, SSO, Module, Betrieb, Migration, Upgrade und Client-Abnahme. Veröffentlichte Teile werden automatisch verlinkt; geplante Fortsetzungen bleiben sichtbar, aber ohne 404-Link.

1. [Install grommunio 2026.06.1: From ISO to Working Groupware](https://forgeone.solutions/en/tech/install-grommunio-2026)
2. [grommunio-antispam with Rspamd: Spam Filtering, Learning and Operations Step by Step](https://forgeone.solutions/en/tech/grommunio-antispam-rspamd-2026-step-by-step)
3. [grommunio-auth with Keycloak: SSO and central login step by step](https://forgeone.solutions/en/tech/grommunio-auth-keycloak-2026-step-by-step)
4. [Set up grommunio Meet 2026 without Keycloak and optionally add SSO](https://forgeone.solutions/en/tech/grommunio-meet-2026-step-by-step)
5. [Set Up grommunio Chat 2026: Teams, Channels, Users and Multi-Tenancy Testing](https://forgeone.solutions/en/tech/grommunio-chat-2026-step-by-step)
6. [Set Up grommunio Files and Office: Validate Files, Web Entry and Online Office](https://forgeone.solutions/en/tech/grommunio-files-office-2026-step-by-step)
7. [Set Up grommunio Archive 2026: Archive, Search and Restore Email](https://forgeone.solutions/en/tech/grommunio-archive-2026-step-by-step)
8. [grommunio MDM 2026 step by step: manage ActiveSync devices safely](https://forgeone.solutions/en/tech/grommunio-mdm-2026-step-by-step)
9. [grommunio Multitenancy 2026: organizations, domains and multiple LDAP sources](https://forgeone.solutions/en/tech/grommunio-multitenancy-2026-step-by-step)
10. [grommunio 2026 Cluster and High Availability: from multi-server lab to tested active/standby homeserver](https://forgeone.solutions/en/tech/grommunio-cluster-ha-2026-step-by-step)
11. [grommunio 2026 disaster recovery and single mailbox restore: backup, full DR and targeted mailbox recovery in the lab](https://forgeone.solutions/en/tech/grommunio-disaster-recovery-single-mailbox-restore-2026-step-by-step)
12. [Migrate IMAP mailboxes to grommunio with imapsync](https://forgeone.solutions/en/tech/grommunio-imap-migration-imapsync-2026-step-by-step)
13. [grommunio: Replace Public Folders with a functional mailbox - step by step](https://forgeone.solutions/en/tech/grommunio-public-folder-functional-mailbox-multiple-domains)
14. [grommunio Web 5.0 in the lab: settings namespace, shared mailboxes and admin impact](https://forgeone.solutions/en/tech/grommunio-web-5-0-in-the-lab)
15. [grommunio 2026.06.2 Upgrade and Technical Acceptance: Keycloak SSO, MFA, AutoDiscover and Mail Flow](https://forgeone.solutions/en/tech/grommunio-2026-06-2-upgrade-keycloak-sso-practice)
16. [grommunio native clients after Keycloak SSO: Thunderbird, Outlook, EWS, EAS and MFA explained (current part)](https://forgeone.solutions/en/tech/grommunio-native-clients-after-keycloak-sso)
17. grommunio Monitoring und Alerting im Betrieb
18. grommunio Security Hardening in der Praxis
19. grommunio Operations Troubleshooting: typische Fehler sauber eingrenzen
