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,458,191
Community Members
 
Community Events
176
Community Groups

Use Crowd for SSO only, not authentication

We are running Jira, Confluence, Bamboo, Stash and Crucible in our environment.  We would like to enable SSO for the applications.  We purchased Crowd but it's not working as I expected (maybe I'm missing something).  I have all the applications setup with their own directories.  It appears that when I add the applications and import the users, I cannot add a user in Directory A to Directory B?  I have to manually add the users for each directory.  That is a lot more work then adding the user directly into the application itself.  My question is can I setup a main directory in crowd that would handle just the SSO, not the authentication for each application?

3 answers

0 votes

I'm not entirely sure by what you mean by "for SSO only, not authentication", but it sounds like you may be after a shared userbase between JIRA, Confluence, etc? If so:

Rather than have a directory per application, it's more common to have a single directory shared by each application configured in Crowd. That means that you only need to add users to a directory once and then that definition will be shared across applications, though you will still need to add them to the necessary groups for that one directory (since Crowd doesn't know which groups are meaningful for the connected applications).

Does that answer your question? If not, please comment and I (or Tiago) will do my best to clarify.

Sorry for the lack of info, new to the Atlassian products. I have Crowd setup as follows: Directories: I have a directory for each app; Jira, Confluence, Bamboo, Stash etc Groups: Each directory has one or more groups, Jira Admin, Jira User etc. What I'm having an issue with is that when I add a new user I have to set them to one Directory, go back and then assign them to a Group under that directory. I'm not able to find a way to add a user and assign them to multiple Groups which is time consuming as I'll need to re-enter the user info in Crowd for each application. I was hoping there is a way to just use Crowd for SSO and not authentication via the apps. We only have about 60 users and add one or two a month so entering them in the individual apps is faster then entering them into Crowd. Unless I'm missing something I'm not really seeing the benifit of having the user authenticate via Crowd since I have to enter them into each individual Directory then take the additional steps of assigning them to a group (most all of the apps assign them to the user group at least).

0 votes

Hi Wesley, I think I didn't understand what you mean by add a user in Directory A to Directory B. Would you mind give a bit more details about the steps you're following? Cheers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events