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

Directory groups can apply to indirect as well as direct members #182

Closed
bhunut-adobe opened this issue May 10, 2017 · 5 comments
Closed
Assignees
Milestone

Comments

@bhunut-adobe
Copy link
Collaborator

When following this guide,
UST returned the following error
Multiple LDAP groups found for: AdobeCCETest-All-App

Current Group Structure

AdobeCCETest-All-App
	AdobeCCETest-South-Pole
	      jadobe2@adobeccetest.com

Log file:
2017-05-10.txt

@phil-levy
Copy link
Contributor

Chester, can your team take a look at this? It may be that the code doesn't quite handle this nested case properly.

@chesterl86
Copy link
Contributor

Sure can.

@chesterl86 chesterl86 assigned ianmak and unassigned chesterl86 May 10, 2017
@phil-levy phil-levy added the bug label May 17, 2017
@ianmak
Copy link
Contributor

ianmak commented May 24, 2017

user-sync doesn't seem to be processing the results of the nested group filter properly at the moment. We are currently planning to refactor this feature to process groups properly, and may support nested groups using a different approach rather than through the LDAP nested group query mechanism.

@bhunut-adobe
Copy link
Collaborator Author

@adobeDan - I just read your comment on the PR. Will this still be included in v2.1 release?

@adobeDan adobeDan added enhancement and removed bug labels Jun 7, 2017
@adobeDan adobeDan changed the title Nested Group - Multiple LDAP groups found Groups in group mappings can apply to indirect as well as direct members Jun 7, 2017
@adobeDan adobeDan changed the title Groups in group mappings can apply to indirect as well as direct members Directory groups can apply to indirect as well as direct members Jun 7, 2017
@adobeDan
Copy link
Contributor

adobeDan commented Jun 7, 2017

No, this will not be in 2.1.1. We thought this was an included feature in 2.0, but it turns out it wasn't. That makes it an enhancement request, not a bug. It will go into a 2.2. Just for you, @bhunut-adobe :), I will try to get 2.2rc1 out next week so you can validate the approach and give it to whatever customer is deperate for it. But no promises about when 2.2 itself will come.

@adobeDan adobeDan added this to the 2.2 milestone Jun 13, 2017
@adobeDan adobeDan self-assigned this Jun 13, 2017
adobeDan added a commit that referenced this issue Jun 16, 2017
Fixes for #182, #129, and #233 - all the requested LDAP improvements
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants