Important Update Effective February 1, 2024!
Due to recent changes in Jira and Confluence, we've made the tough decision to discontinue the OpenID Connect (OIDC)/OAuth app and no longer provide new versions for the newest Jira/Confluence releases as of January 31, 2024.
This is due to some necessary components no longer shipping with Jira/Confluence, which would require some extensive rewrites of the OIDC App.
Important Update! This app will be discontinued soon!
Due to recent changes in Jira, which no longer ships with some components required for our Read Receipts app to run, we've made the tough decision to discontinue the app, as of Februar 5, 2025.
Important Update! This app will be discontinued soon!
We've made the tough business decision to discontinue the app, as of January 11, 2025.
Azure AD B2C with User Sync (SAML)
After completing this setup guide, you will set up Azure AD B2C and your Atlassian product for the SAML SSO app and also User Sync. 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 Custom Policy in 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.
Configure User Sync
- Sign in to http://portal.azure.com.
Select the Directory + Subscription icon in the portal toolbar, and then select the directory that contains your Azure AD B2C tenant.
In the Azure portal, search for and select Azure AD B2C.
- Select App registrations (Preview).
- Select New registration.
- Enter a Name for the application.
- Select Accounts in any organizational directory or any identity provider.
- Under Permissions, select the Grant admin consent to openid and offline_access permissions checkbox.
- Click on Register to proceed.
- Select API permissions in the left panel and then Add a permission.
- Select Microsoft Graph.
- Choose Application permissions.
- Expand Directory and tick Directory.Read.All. Afterward, click Add permissions to continue.
- Click on "Grand admin consent for..."
- It should look like this:
- Click on Certificates & secrets in the left panel, and then click on New client secret.
- Enter a description for the secret and also set an expiry date. Click on Add to confirm.
- 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.
- Go to the overview page of the Azure AD B2C app. Copy the Application ID and the Directory (tenant ID).
- 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.
- Insert the Application ID, Directory ID and the Application secret into the User Sync connector settings.
- To take the full advantages of User Sync, you can enable the Scheduled Synchronization from the Sync Settings tab.
- 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), choose SAML SSO and click Configure.
First Steps - Wizard
- 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. - For the IdP Type, choose "Azure AD". You can also choose a name. Click on "Next" to continue.
- In the next step, you will configure Azure AD B2C. Please keep this tab open or copy the information.
Configure a Custom Policy in Azure AD B2C
For Azure AD B2C, SAML only works via custom policy that you need to create yourself. You can refer to the following Microsoft document for more info about that: https://learn.microsoft.com/en-us/azure/active-directory-b2c/saml-service-provider?msclkid=45673a56c60011ec8f8f44f115d63008&tabs=macos&pivots=b2c-custom-policy
Finishing the Configuration - Wizard
Paste the App Federation Metadata Url that was obtained before from your custom policy in Azure AD B2C
- Click on "Import".
- Click on "Next" to continue.
- For the User Update Method, choose Update with UserSync-Connector. If you additionally want to use the SAML attributes as sent by your identity provider, choose the corresponding option.
- For UserSync-Connector, choose the one you have created before. Then click on "Save & Next" to continue.
Testing SSO
The wizard also allows testing the Single Sign On. Just follow the steps to test if the login works as expected.
- Click on "Start test" to proceed.
- Copy the blue marked link and open a new incognito/private tab or a different web browser. Then, paste the link and navigate to it.
- You will be now redirected to Azure AD's login page. Please log-in with your username and password.
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 "SUCCESS" status, if everything worked as expected.
Click Next to proceed.
SSO Redirection
As a last step, you can set 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.