Goal

After completing this setup guide, you will have a setup for Azure AD B2C and your Atlassian product for the SAML SSO app and also User Sync using the OpenID Connect protocol. Both apps are for Atlassian Server or Data Center products. Additionally, you will enable the SSO redirection and test SSO.

Prerequisites

To use the SAML SSO app with Azure AD B2C, you need the following:

  • An Azure AD subscription
  • An Azure AD B2C Tenant (please check this Microsoft article for more information)
  • A User Flow on Azure AD B2C (check this Microsoft article)
  • A (trial) subscription for the SAML SSO app for Atlassian Data Center or Server applications
  • Admin access to your Atlassian Data Center or Server product

Step-By-Step Setup Guide

Install the SAML SSO app for Atlassian Data Center / Server

In your Atlassian product, open the in-product marketplace as described in the Atlassian documentation.
Search for "resolution saml" and click "Install" for SAML Single Sign On (SSO) by resolution Reichert Network Solutions GmbH.

After the installation is complete, click Manage Apps/Addons. 

Install SAML SSO App

Configure User Sync

  1. Sign in to http://portal.azure.com

  2. Select the Directory + Subscription icon in the portal toolbar, and then select the directory that contains your Azure AD B2C tenant
    Azure AD B2C Switch Directory

  3. In the Azure portal, search for and select Azure AD B2C
    Azure AD B2C

  4. Select App registrations
    Azure AD B2C App Registration
  5. Select New registration
    Azure AD B2C App Registration New Registration (Preview)
  6. Enter a Name for the application
  7. Select Accounts in any organizational directory or any identity provider
  8. Under Permissions, select the Grant admin consent to openid and offline_access permissions checkbox
  9. Click on Register to proceed
  10. Select API permissions in the left panel and then Add a permission
    Azure AD B2C API Permissions
  11. Select Microsoft Graph
    Microsoft Graph Azure AD B2C
  12. Choose Application permissions
    Application permissions Azure AD B2c
  13. Expand Directory and tick Directory.Read.All. Afterward, click Add permissions to continue
    Directory Read All

  14. Click on "Grand admin consent for..."
  15. It should look like this: 

  16. Click on Certificates & secrets in the left panel, and then click on New client secret

  17. Enter a description for the secret and also set an expiry date. Click on Add to confirm

  18. Your Client secret will be displayed only once, thus copy the secret's value. Of course, it is possible to create a new secret, if you lost your secret

  19. Go to the overview page of the Azure AD B2C app. Copy the Application ID and the Directory (tenant ID)
    App Id and Directory ID
  20. Now, it is time to head over to your Atlassian application. In your Atlassian application, go to User Sync, click Add Connector and choose Azure AD
  21. Insert the Application ID, Directory ID and the Application secret into the User Sync connector settings

  22. Since in Azure B2C, the User Principal Name of the users in Azure AD is not really their actual email address, it is recommended to change the mapping of the Username and E-Mail Address attributes in the connector to have the actual email value. In the Provisioning Settings tab, under the Attribute Mapping section, click on Edit for the Username attribute

  23. Choose "Custom" and choose "mail" for the Source Attribute Name, then click on Apply

  24. Do the same for the E-Mail Address attribute

  25. To take the full advantages of User Sync, you can enable the Scheduled Synchronization from the Sync Settings tab (you can do this step later after you validate everything)

  26. Do not forget to save your configuration. Scroll down to the bottom of the page and hit "Save"

Configure SAML SSO

For the next steps, please go to Manage apps (or addons) in your Atlassian product, choose SAML SSO and click Configure.

First Steps - Wizard

  1. After you click "Configure", the Wizard will be triggered. If not, or if you want to add another Identity Prover (IdP) to your existing configuration, click on "+ Add IdP". This guide assumes, that there is no IdP configured.
    The wizard greets you with information, click on "Add new IdP" to proceed
  2. For the IdP Type, choose "Azure AD", and choose "OpenID Connect" for the Authentication Protocol. Give it a name. Click on "Next" to continue

  3. Copy the callback URL to your favourite text editor

  4. In the next steps, you will configure Azure AD B2C. Please keep this tab open to continue later.

Configure the App Registration for the SSO process

Since you have created an App Registration already for User Sync, you can use it for the next steps as well.

  1. Navigate to http://portal.azure.com

  2. Select the Directory + Subscription icon in the portal toolbar, and make sure you have selected the directory that contains your Azure AD B2C tenant
    Azure AD B2C Switch Directory

  3. In the Azure portal, search for and select Azure AD B2C
    Azure AD B2C

  4. Select App registrations
    Azure AD B2C App Registration
  5. Search for the App Registration that you have created for User Sync, and click on it
  6. Under the Authentication tab, click on "Add a platform"
  7. Choose "Web"
  8. In the Redirect URIs field, add the Callback URL that you have copied from the plugin wizard earlier, and click on Configure
  9. From Overview, copy the Application (client) ID and the Directory (tenant) ID to your favourite text editor
  10. Click on Endpoints, and copy the URL of Azure AD B2C OpenID Connect metadata document to your favourite text editor. Make sure to replace <policy-name> in that URL with your User Flow name (you must have a User Flow created - check this)
  11. Create a User Flow, if you don't have one already created (check this Microsoft article)
  12. In your User Flow, under the Application claims tab, make sure that at least the Email Addresses and the User's Object ID are selected. You can select other claims as well if you want, but those are the mandatory ones for the app
  13. Now, back to the wizard in your Atlassian product. Enter the Client ID and the Client Secret that you have copied from before
  14. For now, just enter the Tenant ID, but we will change that later, since the current wizard doesn't support the User Flow of Azure AD B2C, then click on Import Metadata
  15. You can enable the Single Logout if you want to, then click on Save and Close
  16. In the configuration, scroll down to the OpenID Connect Client Settings section, and click on Show Advanced Azure AD Settings
  17. Change the OpenID Connect Directory URL with the URL that you have copied earlier of Azure AD B2C OpenID Connect metadata document, then click on Import Metadata
  18. Scroll down to the User Creation and Update from UserSync-Connector section, and choose your connector that you have created earlier
  19. Scroll down to the How to search for user to login section, and click on Edit.
  20. If you have followed the recommendation in the User Sync connector attributes mapping for the username, then change the mapping here as well to "emails", as follows.
  21. Click on Apply, then make sure to Save the SAML SSO configuration.

Testing SSO

  1. In the System & Support tab, scroll down to the Tracker List section, click on New Tracker and choose the IdP name that you have just configured


  2. Copy the tracker URL and open a new incognito/private window or a different web browser, then paste the link and navigate to it

  3. You will be now redirected to Azure AD B2C's login page. Please log-in with your username and password

  4. If everything worked fine, you will be logged in to your Atlassian product. In the other tab/browser in which you were configuring the SAML SSO plugin, you can see also the "LOGGED_IN" status, if everything worked as expected.

SSO Redirection

As a last step, you can enable the Enable SSO Redirect option. If set, all users will be redirected to Single Sign On, thus they will be logged in via the IdP.
Click on Save & Close to finish the configuration.