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.

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

Configuring an OU for groups augmentation not possible #29

Closed
engineererr opened this issue Nov 30, 2017 · 2 comments
Closed

Configuring an OU for groups augmentation not possible #29

engineererr opened this issue Nov 30, 2017 · 2 comments
Assignees

Comments

@engineererr
Copy link

Scenario:

  • We connect to a sub OU in the LDAPCP general settings to show only people from the employees OU in the people picker:
    campany.ch/users/employees
  • The AD claims provider is set to invisible
  • We don't want to include another OU: company.ch/users/students
  • We need groups augmentation but the groups are not in the employees OU

Problem:

  • We can't find groups because they are not in the employees OU

Workaround:

  • We changed the OU to users root (company.ch/users) and configured filters to exclude users from students OU

Request:

  • We'd like to configure a seperate LDAP base DN to query AD-groups for augmentation.
@Yvand
Copy link
Owner

Yvand commented Dec 11, 2017

Hi @kurky91, thank you for the clear explanation.

I understand the need but this sounds very specific and requires some effort to update the admin page to propose this new setting while not making it confusing.

Besides, you can already do what you want by creating a custom version of LDAPCP and override method GetLDAPServers(RequestInformation).
Object RequestInformation contains the type of operation (augmentation, search, validation), so you can return a LDAP path different based on that.

You can find more information on http://ldapcp.com/For-Developers.html and practical example in "LDAPCP.Developers.zip" that you can find with each LDAPCP release.

The drawback is that it's of course more work than just deploying LDAPCP, and you would lose the administration pages unless you create additional code to be able to use them with your own claims provider.
Would this be an option for you?

@Yvand Yvand self-assigned this Dec 11, 2017
@engineererr
Copy link
Author

Hi @Yvand

Thank you for your response and all of your work you put into LDAPCP.

We are thinking about extending LDAPCP in the future to support a directory differently to LDAP that allows us to access it through REST endpoints.

Thanks for your suggestion, I'll consider it if the clients decides to extend LDAPCP for his purposes.

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

No branches or pull requests

2 participants