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 way to configure directories in Crowd?

We are running Crowd with Jira, Fisheye and Crucible in our company with about 500-1000 users.

What are the best practices in configuring Crowd directories to control authentication to each application? We are using a delegated authentication directory and will have many users needing access to all applications and many different groups.

Would it be best to create one Crowd directory containing all of the users/groups for each application ex.

  • Company directory
    • jira-users
    • jira-administrators
    • jira-developers
    • fisheye-users
    • fisheye-administrators
    • fisheye-developers
    • crucible-users
    • crucible-administrators
    • crucible-developers

~OR

Create a separate Crowd directory for each application ex.

  • Jira directory
    • jira-users
    • jira-administrators
    • jira-developers
  • Fisheye directory
    • fisheye-users
    • fisheye-administrators
    • fisheye-developers
  • Crucible directory
    • crucible-users
    • crucible-administrators
    • crucible-developers

Also we will be using SSO-- is this configurable with both options?

Thanks!

2 answers

1 accepted

1 vote
Answer accepted

I thik it really boils down to how users will use the various tools. If everyone will use everything and can see everything, I'd keep things simple and use the same group to control similar access on all tools. For example, create a "users" group, dump everyone in there and grant the "users" group permissions to log in and do basic functions on each application. If you have more distinction with your userbase, you might need to break things up as you suggest. I see companies that do this both ways. It just depends on your license and security situation. I'm in favor of not adding complexity for complexity's sake, personally.

If your situation permits, I recommendone Crowd directory as Dave mentioned. If you have multiple Crowd directories, you have to add a user who will use all of Jira, Fishehe and Crucible into each directory. It's a troublesome task.

You can also use multiple Crowd directories in order to use multiple directory types. For example, one direcory is LDAP Delegated Authentication and another is Crowd Internal Directory.

Thanks Shun!

Will all of the groups within that directory show up in each application?

If so, does that count towards the license limit in the application?

Yes all groups will show up in each application.

But only the people who can actually log into your application count towards your license limit.

Best regards,

Peter

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

☕️ Monday coffee with Jexo: Weekly Atlassian news roundup | 21st June 2021

Hi community 👋, as every Monday we're bringing you a quick update on what happened in the Atlassian ecosystem last week. There were a few interesting events like for example the announcement of th...

66 views 0 6
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