Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira Directory LDAP configuration grabs too much information for the Directory

Watson Prunier
Contributor
April 5, 2019

Below are pictures of my network (remade for security purposes but very close).

The Jira Developers group has the list of Jira Users to be added to the jirausers group.

The Jira Developers path is:

CN=Jira Developers,OU=JiraGroups,OU=Groups,OU=Shire,OU=Middle Earth,DC=MY,DC=KINGDOM,DC=COM

My base DN should be DC=MY,DC=KINGDOM,DC=COM, correct?

And the Additional Group DN should be CN=Jira Developers,OU=JiraGroups,OU=Groups,OU=Shire,OU=Middle Earth, correct?

My biggest problem is that instead of importing the 300+ names in the Jira Developers group, the system grabs all 50,000 user objects (45K, if I filter out the disabled accounts) higher up the tree.

No configuration I use will take only the users in the group. What am I doing wrong?

ADUC.pngjiracfg.png

1 answer

0 votes
Mikael Sandberg
Community Champion
April 5, 2019

You are not limiting the search of the users, you added the limit to the Group DN instead of the User DN, and that is why you get all 50k users. So add CN=Jira Developers,OU=JiraGroups,OU=Groups,OU=Shire,OU=Middle Earth to the User DN instead.

In my environment I do not import groups so I use a dummy group search instead as described here.

Suggest an answer

Log in or Sign up to answer