You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I am currently using CROWD for LDAP and having problem loading the users.
I guess I will have to explain my problem first..
Our company LDAP contains over 10,000 accounts and over 100 groups.. and in that LDAP, we have a AD group that contains 50 accounts.
On Crowd setting up the LDAP, I set Base DN as where ALL accounts are in there.. which is over 10,000 accounts.
and on configuration page, I leave User DN blank, and set the Group DN as the location of the Group which should contains 50 accounts..
When I update this, it loads ALL the accounts in LDAP and just that specific group.
When I set Base DN as the location of the Group that I want to use, and leave everything blank, it loads JUST THAT GROUP but not the accounts...
I am guessing it is because account belongs to different AD or different location than the Group...
How can I just load the Group that I want to use, and the accounts in that Group only?
The users and groups in LDAP are separated objects.
The Base DN is the root location for JIRA to search in the AD.
When you leave the User DN blank you tell JIRA to search all users from that Base DN root, if your search pattern is default.
When you specify the Base DN to the specific group path is expected to get only that group. Since the user search will be done over that specific path that probably does not contain any user object.
I believe you need the first configuration that get all the users and the specific group and change the users filter to something like this:
This will filter all users that are member of foo group.
Daniel P santos