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

Can Crowd and SSO be implemented separately?

SSO is a feature of Crowd

Therefore, SSO can be used to authenticate to the Atlassian suite, JIRA, Confluence and JSD. 
AND Crowd used to manage Atlassian suite users?

 image2017-1-3 13:3:13.png

Currently users are managed internally in each JIRA, Confluence and JSD which is very labor intensive.

If Crowd is implemented, with the inclusion of SSO for authentication as on this diagram, does SSO nullify Crowd?

Converting internal users to Crowd should have no impact on existing SSO?

Your insight is appreciated.

 

 

 

2 answers

1 accepted

1 vote
Answer accepted
Marcin Kempa Atlassian Team Jan 03, 2017

Hi @Janene Hoffmann

From your diagram I read that you are using SAML SSO with a separate IDP. The SSO provided by Crowd does not implement SAML specification. However you may use Crowd only for authorisation and user management just like any other external directory and still take advantage of other ways of authentication like SAML SSO.

Using Crowd for user management does not imply that products connected to it must use the SSO provided by Crowd. Therefore implementing Crowd and exporting internal users from products to it should not have any impact on existing SSO solution you are using.

As a side note, since you are using SAML SSO, you may be interested in latest JIRA 7.3 Data Center releases which comes with SAML integration out of the box.

Thank you for helping me understand what has been designed!  Obviously I'm not familiar with SSO nor Crowd, but need to get up to speed quickly. Also, before I get too far into converting Internal Directory to Crowd, I need to feel confident of the path I've been directed towards. 
So I can convert all the Internal Directory groups and users to Crowd without impacting SSO.
Thank you for the clarification!

0 votes

Hello Janene!

In case you havent implemented SSO yet, you might want to check out Kantega Single Sign-on.

We do SSO with Kerberos and SAML even for users in the internal directories.

Have a look at https://marketplace.atlassian.com/search?query=kantega 

If you need any assistance, email us at SSO@kantega.no

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events