Repository navigation
Maintenance: State that Kerberos SSO only signs in existing users. - #954
Merged
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.