It is possible to create a quick login for your helpdesk via SAML for Enterprise SSO integrations.

A working SAML Identity Provider (IdP) such as Keycloak, Redhat SSO Server, ADFS, Okta, etc.
Please Note:

Testing has confirmed working deployment with Keycloak 7.0.0. But should also work with any standard SAML compliant IdP.

Configuring the upstream SAML IdP is outside the scope of Zammad documentation.

Configure SAML in Zammad

  • Navigate to “Admin -> Security -> Third Party Applications -> Authentication via SAML”
  • Click the on/off slider to “On”

Define the fields per your upstream IdP documentation, some known working Keycloak IdP values are provided for reference.

IDP SSO target URL:



This will vary according to your IdP documentation

IDP certificate: (base64 encoded Public Cert from the SAML IdP):



  • The above certificate is just an example, you should use a proper certificate from your IdP!
  • Note that this is generally NOT the same cert used by TLS in the HTTPS connection to the IdP.
  • In Keycloak, this certificate can be found by going to:
  • Keycloak Admin: Realm settings -> keys -> RSA -> “certifcate” popup
  • Paste as a single line string with no line breaks.
  • Do not set this option at all if using the “certificate fingerprint” for cert validation.

IDP certificate fingerprint: Optionally use the fingerprint instead of the certificate itself for cert validation. Because sha1 is used for the fingerprint, this option is not preferred. Do not set this option at all if using the “certificate” field above.

Name Identifier Format:


Configured example:

Zammad SAML Example

Configure the SAML IdP

If your IdP supports xml import or auto xml metadata retrieval, use this URL: https://zammadFQDN/auth/saml/metadata

For Keycloak IdP, save the contents of that metadata file as “metadata.xml” and then log into Keyclaok and import it as a new Client.

Keycloak sends the “Username” in whatever format your users are stored in. The tested SAML instance used email address for the “username”, but Zammad also needs to see an “email” attribute to correctly automap to existing users. In Keycloak, we can create a “Mapper” for the newly imported Zammad client.

Goto -> Keycloak Admin -> Clients -> https://zammadFQDN/auth/saml/metadata -> Mappers -> Create

Name: ZammadEmail
Mapper Type: User Attribute
User Attribute: emailAddress
SAML Attribute Name: email
SAML Attribute NameFormat: Basic

Keycloak needs to know the redirect location in advance for security: Goto -> Keycloak Admin -> Clients -> https://zammadFQDN/auth/saml/metadata

Valid Redirect URIs:


For other IdP systems, you can configure things manually. Zammad is using POST Bindings for the Assertion Consumer Service (ACS)



Zammad requests these attributes from the SAML IdP, these are not configurable. Each attribute should map to the correct SAML attribute via “Mappers” as needed, or equivalent mapping paradigm in other IdP systems. The specific attributes to map vary widely between SAML IdP systems, this requested attribute list can help align the SAML provided attributes with what Zammad expects to see.

RequestedAttribute FriendlyName="Email address" Name="email" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic" isRequired="false"
RequestedAttribute FriendlyName="Full name" Name="name" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic" isRequired="false"
RequestedAttribute FriendlyName="Given name" Name="first_name" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic" isRequired="false"
RequestedAttribute FriendlyName="Family name" Name="last_name" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic" isRequired="false"

Now, you should be able to link accounts in the Profile Panel under Linked Accounts, or log in via the Zammad login page. Alternately, you can enable automatic account linking for existing user accounts.