LDAP / Active Directory¶
Zammad comes with a powerful LDAP integration that allows you to have a single source of truth. By this you reduce the number of login credentials your user has to remember.
- 📝 Manage LDAP-Sources
Add, modify, remove or re-arrange your LDAP-Sources as needed.
Before you continue, please note the following limitations.
Mapping / Synchronizing organizations is not possible
You may want to consider using domain based assignments to overcome this issue. Learn more on Unternehmen.
Zammads LDAP sync is one way. Editing user settings or permissions may be overwritten upon the next sync depending on your configuration.
Nested groups are not supported.
Synchronizing user avatars from LDAP is not supported.
Unlike user filters, group filters cannot be changed.
When a user originates from an LDAP server, Zammad will try to verify the login credentials against LDAP first - if this fails Zammad will check its local database.
Users can have local passwords even if they’re LDAP users! You can learn more about user accounts in general on Benutzer.
When several LDAP sources contain the same user (meaning the same email address), the user in question will be updated with every source configured. The last LDAP source will win.
This is subject to change with Issue 4109 in the future.
Synchronization statistics currently affect all configured LDAP sources. This also applies for newly added or updated sources.
This is subject to change with Issue 4108 in the future.
Zammad currently has limited fallback server support. You can workaround this by providing several sources - however, ensure to have the exact same configuration on your fallback.
This is subject to improve with Issue 4107 in the future.
This section holds all requests Zammad handled for all LDAP sources. These entries can either contain synchronization information or logins (authentication attempts via Zammads login interface).
By clicking on any request, Zammad will provide even more information. The provided information can be useful when something does not work as expected.
Especially a LDAP synchronization can cause many log entries. The web interface will always limit the number of shown entries to the last 50 entries.