Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

setting up crowd user directory with AD

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.


  • Connected to Crowd via an LDAP connector (e.g. for Active Directory), with all authentication and user/group management in LDAP.
  • A Crowd internal directory for user/group management but with authentication delegated to LDAP (e.g. Active Directory).


1 answer

0 votes

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.



Hello Craig,

How do you manage an application(for example-bitbucket) users and groups in Crowd?

Hey Reneesh,

We have a number of methods as we have a variety of backend user sources:

  • Active Directory 1 (~30,000 staff) - users and groups come from AD based on Group filters. Membership is managed in AD directly, or a custom web application that allows identified staff to manage membership which is pushed in to AD
  • Active Directory 2 (~3,000 staff) - same as Active Directory 1, however we may be moving the Groups to Crowd as the team that manage the AD memberships have a turnaround time that does not align with business needs and the web-app is only available from inside the corporate network which some offices are not connected to
  • LDAP 1 (~30,0000 staff) - users come from LDAP, groups are added in Crowd. Custom web application that uses the Crowd APIs to allow identified users to manage groups they're responsible for (this was built before the Crowd Delegated Group Admin function was released (
  • LDAP 2 (~2,000 staff) - users and groups come from LDAP, based on LDAP group filter.  Membership is managed in a custom web application that allows identified staff to manage membership which is pushed in to LDAP
  • Crowd internal users and groups (any other users not part of the above 4 directories) - users and groups in Crowd, Membership management same as LDAP 1


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

181 views 6 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you