Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,547
Community Members
 
Community Events
176
Community Groups

Crowd timing out when querying Active Directory

I've set-up crowd to query my organization's AD server. Unfortunately, our users are in different OU's off of the root. When crowd is configured to search from the root, it time's out immediately. Increasing the LDAP connection time-out does not appear to have any affect. To work around this, I've had to create a different Directory for each high level OU. This causes our groups to appear multiple times.

Our Confluence instance currently authenticates against the AD (searching off of root) without issue.

How can I configure Crowd to properly query from the root and not time out.

2 answers

Our AD is a read-only DC. Due to where on the network that Crowd and Confluence are installed, they cannot talk directly to the main AD servers.

0 votes
Ivar Rising Star Nov 09, 2011

Will Crowd connect every time you try, or is it sometimes unable to?

We had similar issues with Crowd, and the reason turned out to be the fact that the AD was load balanced. Once I connected to the internal IP adress of one of the AD servers, everything went fine and searches was really fast.

I'm not sure, but I believe that the connector towards AD is different for Confluence and Crowd, so this might be the reason why Confluence works just fine while Crowd have issues.

If load balanced AD, try connecting directly towards one of the internal IP addresses and see if you can notice any change.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events