Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix Zammad integration with AD #32

Open
fredreichbier opened this issue Sep 1, 2017 · 2 comments
Open

Fix Zammad integration with AD #32

fredreichbier opened this issue Sep 1, 2017 · 2 comments
Labels
prio:low

Comments

@fredreichbier
Copy link
Contributor

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
Copy link
Contributor Author

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 pushed a commit that referenced this issue Sep 5, 2017
Add an option to ignore SEARCH result references
6030378 
Working on #32
@fredreichbier fredreichbier mentioned this issue Sep 6, 2017
Merged
@fredreichbier
Copy link
Contributor Author

Upstream has added basic support for LDAPSearchResultReference: twisted/ldaptor@35bc45b

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
prio:low
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@fredreichbier