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's the correct way to use Groups for Crowd using SSO?

I've been playing a bit with Crowd integration with JIRA and Confluence and using SSO. I have a single user base (just employees of my company). I want to use Single sign on between JIRA and Confluence.

I have JIRA 4.2.3, Confluence 3.4.9 and Crowd 2.3.3

Two questions:

  1. How many user directories should I have in Crowd? One directory for all employees, or one for each of JIRA and Confluence (where each employee has an account in both)?
    I assume it's one directory (Single Sign On doesn't appear to work when I add my users to both a JIRA and Confluence directory)
  2. Assuming I should go with one directory, how should I do groups? I have Confluence groups that I don't want to show up in JIRA, and I have JIRA groups that I don't want to show up in Confluence. But when I have a single directory, and I add a Confluence group to a user, that group also appears in JIRA for that user. And vice versa.

Any tips on how this should be set up?

1 answer

1 accepted

0 votes
Answer accepted

Use one directory and use groups in the applications to control athentication into the applications. Yes you will see all the groups from the directories in each application but those groups don't need to have 'use' permissions to those applications.

Oh and I guess, the group assignments etc.. really have nothing to do with SSO. You can't have some users supporting SSO and others not (that I'm aware of anyway)

Thanks for the confirmation. SSO only plays in because then I can't use different directories for different applications. If I wasn't using SSO, I could create a directory for each app, with identical user names in each, and keep the groups separate.

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...

321 views 9 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