Skip to content

Maintenance: State that Kerberos SSO only signs in existing users. - #956

Merged
suelje merged 1 commit into
zammad:mainfrom
suelje:sso-requires-existing-users-bp
Nov 17, 2026
Merged

suelje merged 1 commit into
zammad:mainfrom
suelje:sso-requires-existing-users-bp

Conversation

@suelje

@suelje suelje commented Nov 17, 2026

Copy link
Copy Markdown
Member

Backport of #954 to the 7.2 documentation.

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.

The behaviour is the same in 7.2.3: SessionsController#create_sso, the LDAP sync's skip rule for users without mapped attributes and the LDAP wizard's default mapping samaccountname → login are unchanged on stable.

🤖 Generated with Claude Code

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 '<name>' 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.
@suelje
suelje requested a review from ralf401 November 17, 2026 13:07
@suelje
suelje merged commit 85716c0 into zammad:main Nov 17, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants