Matrix and Keycloak SSO integration
Signing Matrix users in through Keycloak, either with Synapse's built-in OIDC provider support or through Matrix Authentication Service, including back-channel logout and what changes when you adopt MAS.

Identity providers and third-party chat networks that a self-hosted Matrix homeserver is commonly connected to, as the Synapse, MAS and bridge projects document them.
Signing Matrix users in through Keycloak, either with Synapse's built-in OIDC provider support or through Matrix Authentication Service, including back-channel logout and what changes when you adopt MAS.
Letting Matrix users log in with directory credentials: the matrix-synapse-ldap3 module and its maintenance status, why it does not work with Matrix Authentication Service, and the Dex route the projects recommend instead.
Running mautrix-slack so teams can keep Slack channels, Slack Connect channels and DMs reachable from Matrix during a transition, and which message features cross the bridge in each direction.
Self-hosting the mautrix WhatsApp, Signal and Telegram bridges so staff can reach external contacts from Matrix, what each bridge supports, and the data-handling questions bridging raises.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.