From dee460ea8d66627b066a2ba2c050ed8e0aa4752f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Silke=20Ja=CC=88nichen?= Date: Mon, 16 Nov 2026 19:47:38 +0100 Subject: [PATCH] Maintenance: State that Kerberos SSO only signs in existing users. The SSO guide promised that everyone with an intranet account automatically gets a Zammad account. Zammad never creates accounts on SSO: it looks up an existing user by login, ignoring case, and refuses the sign-in with "User '' could not be found." otherwise. The guide now says so in the overview, lists a matching Zammad account (login = sAMAccountName, as created by the LDAP integration) as a requirement, and adds a troubleshooting entry for the error, including the LDAP sync skipping users without first name, last name and email address. --- appendix/single-sign-on.rst | 36 ++++++++++++++++++++++++++++++------ 1 file changed, 30 insertions(+), 6 deletions(-) diff --git a/appendix/single-sign-on.rst b/appendix/single-sign-on.rst index fdf01ee0..3945f5c0 100644 --- a/appendix/single-sign-on.rst +++ b/appendix/single-sign-on.rst @@ -19,9 +19,13 @@ authenticating them, and managing their sessions. If your IT department keeps its own user identity store (like Active Directory), Zammad's SSO support allows you to leverage that existing auth system -so that anyone with an account on your local intranet will -1) automatically have an account in Zammad and -2) be able to log in with a single click. +so that users with an account on your local intranet can log in to Zammad +with a single click. + +SSO only signs in users who already exist in Zammad; it never creates +accounts. Use the :admin-docs:`LDAP integration +` to create the Zammad accounts for your +Active Directory users and keep them in sync. .. note:: If you *don't* have this IT infrastructure but still want one-click login, @@ -86,11 +90,16 @@ You will need: - root access - a fully-qualified domain name (FQDN) +- a Zammad account for every user who signs in via SSO, whose **login** is the + user's Active Directory user name without the realm (``sAMAccountName``). + The :admin-docs:`LDAP integration ` + creates these accounts and maps ``sAMAccountName`` to the login by default. + - some familiarity with system administration (*e.g.,* Apache configuration) -For best results, set up :admin-docs:`LDAP integration ` -to make sure your Active Directory and Zammad user accounts -are always in sync. +.. note:: Zammad matches the user name against the login only, ignoring + case. An account whose email address matches but whose login differs is + not found. .. _sso-register-spn: @@ -555,6 +564,21 @@ Troubleshooting within five minutes of each other? (Kerberos is a time-sensitive protocol.) +Errors in Zammad +^^^^^^^^^^^^^^^^ + +"User '' could not be found." + Kerberos authentication succeeded, but Zammad has no user whose login is + ````. SSO does not create accounts. Make sure the user exists in + Zammad and that their login matches their Active Directory user name, + *e.g.,* by running the :admin-docs:`LDAP integration + ` with ``sAMAccountName`` mapped to + the login. + + The LDAP integration skips Active Directory users whose first name, last + name and email address are all empty, so these users never get an account + in Zammad. Fill in at least one of these attributes in Active Directory. + Errors in Apache Logs ^^^^^^^^^^^^^^^^^^^^^