Atlassian SSO

[Won Je Choi]

Can JIRA and Confluence be directly pointed to o365 SSO without any addons?

[Lars Olav Velle]

Hello @Won Je Choi

Simple answer. This cannot be achieved without an add-on or crowd. 

With Kantega Single Sign-on you can sync users and groups directly into the application and you also get SSO.

There is no need to buy crowd using our add-on. (one less application to buy and mange) 

https://marketplace.atlassian.com/search?query=kantega

Give it a spin and let us know what you think. 

You can reach us at sso@kantega.no 

[Bruno Vincent]

Hi @Won Je Choi

It depends on which version you're talking about:

• The Datacenter version does support SAML authentication with Azure Active Directory
• The Cloud version also supports SAML authentication with Azure AD
• For server editions, you will actually need an add-on

[Won Je Choi]

Hello @Bruno Vincent,

Thank you for the reply. So since we have our JIRA and Confluence servers in our AWS server, we would nee an add-on such as Crowd SSO? and there is no way for us get it setup without it?

[Bruno Vincent]

Well, Crowd is not a third-party add-on, it is an Atlassian product. But you could actually use it to get SSO between your Atlassian applications (you would need to configure an Azure AD connector in its console for this). Please note that it's not really O365 SSO though:

• With Crowd, you will need to login once into one of your Atlassian application (e.g. into Jira) and then you will not have to enter your credentials again to browse to your other Atlassian applications (e.g. Confluence). The first time you log in, you enter your O365 username and password in the Atlassian application's login form
• With O365 (through a third-party add-on), when you try to connect to your Atlassian application (e.g Jira), you will be redirected to Microsoft's O365 login page. If you already have a session on O365, then you will not need to enter your credentials again and you will immediately be redirected back to Jira without needing to authenticate.

I hope the two different use cases are clear enough now :-)