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

Your Points Tracker
Challenges
Leaderboard
  • 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
Recognition
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?
Kudos
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

What is the best practice for Crowd configuration?

Hello, I can't figure out how to proceed after reading Crowd 2.2 doc. Please help and provide suggestion. Currently we are using 50-users license. Crowd is to provide SSO for all applications. All users and groups are stored in OS X Server Open Directory. The number of users already exceeeded 50, and growing. The users are grouped into JIRA groups, Confluence groups and others. Only a small portion of the users will authenticate with Crowd. I think the best configuration for Crowd is "Connected to Crowd via an LDAP connector (e.g. for Active Directory), with all authentication and user/group/role management in LDAP." But my question is, Crowd might consider all my 100+ plus users towards the 50-users license. Is the above approach not suitable? Should I store the users n groups in Crowd and authenticate to OD instead?

1 answer

1 accepted

0 votes
Answer accepted

It sounds like you are close to having it right.

Basically with crowd licensing, 1 Crowd License Seat is defined as a user who can authenticate to 1 or more applications.

http://www.atlassian.com/licensing/crowd#downloadlicenses-5

What you need to enusre is that only the groups you defined above for the variuos applications are the groups that are assigned to those applications and that under Directories in each Application, the allow all to authenticate is set to FALSE.

This means only the groups you specify for that application will allow those users to authenticate.

This will limit the number of users that crowd will calculate for its license count

Hello Collin, thanks for the reply. Does it mean I can still keep the users n groups in OD, n have those groups defined in Crowd such that the number of actual users is controlled?

Yes, keep them in OD, but assign the groups that you want to use for users of an application to that application under the Application Tab

Suggest an answer

Log in or Sign up to answer
TAGS
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