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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We're setting up a new crowd instance and looking for recommendations to configure directories with AD. As per crowd documentation we can configure with AD using following methods. Please share your experiences and best practices from these two methods.
Hi Reneesh,
Having dealt with a variety of Crowd environments and connectors before, I would suggest not using the delegated connector. Having the LDAP connector with caching on has given us much more control over changes in the past (especially when changing the username format from samAccountName to email field) - just make sure you correctly map the uniqueUserId field to the unique field in your AD.
CCM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Craig,
How do you manage an application(for example-bitbucket) users and groups in Crowd?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Reneesh,
We have a number of methods as we have a variety of backend user sources:
CCM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.