SingleSignOn: How to enable SSo for multiple sites under single oranization?

[Pramod Kumar Mandadapu]

Hi Team,

We have one organization with two cloud sites one is production instance and second one is test instance.

We are trying to enable SAML SSO  by following below link:

https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/atlassian-cloud-tutorial#configure-atlassian-cloud-sso 

As per the above mentioned guide in one of the step we have to provide our instance details.

On the Basic SAML Configuration section, if you wish to configure the application in IDP initiated mode, enter the values for the following fields:

a. In the Identifier text box, type a URL using the following pattern: https://auth.atlassian.com/saml/<unique ID>

b. In the Reply URL text box, type a URL using the following pattern: https://auth.atlassian.com/login/callback?connection=saml-<unique ID>

c. Click Set additional URLs.

d. In the Relay State text box, type a URL using the following pattern: https://<instancename>.atlassian.net

so my question here what should we provide in the Relay state text box (point d). If we provide only one of the instance link test site/prod site. Will the SSO is enabled only for that particular instance?

Also in other step it is mentioned that 

Click Set additional URLs and perform the following step if you wish to configure the application in SP initiated mode:

In the Sign-on URL text box, type a URL using the following pattern: https://<instancename>.atlassian.net .

What is the difference between  IDP initiated mode and SP initiated mode. Do we need to both the steps?

[Dave Meyer · Accepted solution]

Hi @Pramod Kumar Mandadapu ,

When you configure SSO, it applies to all instances of all Atlassian products, regardless of whether the sites have been linked to your organization. The linking of sites to your org drives other features like the audit log and admin insights, and helps you collect everything in one place. But part of our promise with SSO is that it will cover all users in your company, regardless of what products or instances they are using.

IdP-initiated auth mode means that SSO is triggered from Azure AD. So a user would click the "Atlassian Cloud" application in the Azure AD "My Apps" portal and be automatically logged in to your instance. So since most users will expect this to point to your production instance, you should use your production instance URL here. SSO will still work for your test instance, you will just need to navigate to it directly in your browser.

SP (service provider) initiated auth starts on the Atlassian side. So if a user goes to an instance, and they haven't logged in, they will be redirected to Azure AD to authenticate. You'll likely want to use your production instance URL here as well, but you can still navigate to your test instance directly in the browser and it will still redirect you to Azure AD if you haven't logged in.

Hope this helps.

Dave

[Pramod Kumar Mandadapu]

Hi Dave,

Thanks for the response. It's working :).