Fix Zammad integration with AD

fredreichbier commented 7 years ago

Zammad integration is currently a bit tricky:

Zammad does a few things that make the LDAP proxy hiccup, e.g. it seems like it closes the LDAP connection before all search results have been sent. We should check that the LDAP proxy handles these cases gracefully.
If we pass the whole DC as the Base DN, the LDAP proxy is confused because the response contains referrals in the case of AD (see this issue). If we pass CN=users,... as Base DN, Zammad cannot find any groups and refuses the proceed.

fredreichbier commented 7 years ago

We can work around problem 2 if we just throw away all LDAPSearchResultReference responses, as they are probably ignored by the apps anyway. However, the proxy won't be very transparent anymore in that case.

fredreichbier commented 5 years ago

Upstream has added basic support for LDAPSearchResultReference: https://github.com/twisted/ldaptor/commit/35bc45b27c24e938766519a10435a3dbee719da6

privacyidea / privacyidea-ldap-proxy

Fix Zammad integration with AD #32