Atlassian Cloud SSO (Single Sign-On) for Azure AD using SAML
Jira SAML Single-Sign On(SSO) for Atlassian Cloud allows you to securely login using Azure AD credentials. Single Sign-on (SSO) into your Atlassian Access or Atlassian Jira Cloud Account with any of your existing Identity Provider credentials for enhanced security and features using our module.
You can refer the steps to configure Multiple IDPs and Domain Mapping in Atlassian Access from the video or documentation given below
Atlassian Guard is an additional subscription applied across the Atlassian Cloud products like Jira Software, Jira Service Management, Jira Work Management, Confluence, and Bitbucket. It is needed for Single Sign-On (SSO) or any Cloud Service that comes under Atlassian Guard.
2. Domain Verification:
The first step of Atlassian Guard starts with the Domain Verification process to enforce SSO on the managed user accounts. This process verifies that you own a valid domain for managing the user accounts and use the same domain name for the email addresses.
Download And Installation
Log into your Jira instance as an admin.
Navigate to Apps → Explore more apps from the header menu.
Go to Apps and click on the Add Application button.
In Choose Application Type click on All Apps dropdown and select
SAML/WS-FED
application type.
Search for Atlassian Cloud (SAML) in the list.
Enter the following values in the respective fields, you will receive these values after
creating an app in Atlassian access. Refer this step.
Custom Application Name
Any name would be fine
SP Entity ID or Issuer
You will receive after configuring Atlassian Access App
ACS URL
You will receive after configuring Atlassian Access App
Also make sure that Sign Response & Sign Assertion both options are turned
ON. Then click on the Save button.
Once the App is successfully Created, Select that App and then click on Metadata option to
get app’s Metadata.
Since we are using miniOrange as a Brokering Service in this solution, Go to Information required to
authenticate via external idp section as highlighted, and Click on Show Metadata Details.
After clicking on the Show Metadata Details button you can see the metadata details.
You will need these details while configuring an Atlassian
Access app.
In the left sidebar hover on Users then click on
Users List
Click on Add User and enter details to enforce Single Sign On(SSO) on that user.
Make sure that the user created here will also exist in the Atlassian Cloud.
Select your organization and then select the Security tab. Click on SAML Single
Sign-On from the left sidebar.
You can click on Instructions for different Identity Providers. It provides a help page
for specific IDP and Attribute Names for Attribute Mapping.
Here you will get the SAML Configuration Instructions for different identity providers
as listed. Click on Got it.
Click on Add SAML Configuration.
You will be redirected to the Add SAML Configuration window. Enter IDP Entity
ID, SSO URL and the public certificate.
Click on the Save Configuration button.
You will get these details in the metadata details section after configuring the miniorange
app. Refer this step
Now you will be shown SP Entity ID & SP ACS URL as shown below.
These details will be needed in miniOrange app configuration.
Now set up the Authentication Policies by clicking on the View Authentication Policies.
Click on Add Policy.
Enter the policy name and add the policy.
Now under Single Sign-On, click on Enable Single Sign-On.
Then click on the Members tab besides the settings tab and click on Add
Members.
The Single Sign On(SSO) will work only for Added Members.
Enter details and click on Add Members.
The user must be present in both Atlassian and miniOrange.
Step 3. Test Atlassian Cloud - miniOrange
Configuration
Go to Atlassian Login Page.
Enter email and click on Continue. Then you will be redirected to miniOrange Login Page
After logging into miniOrange, you will be successfully logged into Atlassian Cloud Dashboard
Now, you will be able to Login to your Atlassian Dashboard using miniOrange Credentials.
If you
do not have any IDP, you can always go with miniOrange IDP.
From the left navigation bar select Identity Provider
Click on Add Identity Provider button.
Select SAML tab.
You can get the metadata details of miniOrange app either by clicking on the link
shown by "Click here" in the yellow block, Or you can also get the details after creating the
app. Keep these details handy as we will need these in configuring Azure AD.
Click on Show Metadata details under For SP - INITIATED SSO. You can
either manually enter details or use Metadata URL or File
Now to add SAML app for Azure AD, go to Add Identity Provider page and click on Import IDP Metadata.
Import the metadata file that you will get from Azure AD. Refer this step.
If you don't have a metadata file, you can also provide the details manually. You need to configure
following endpoints:
IDP Entity ID
Entity ID of IDP
Single Login URL
Login Url from IDP
Single Logout URL
Logout Url from IDP
X.509 Certificate
The public key certificate of your IDP.
Few other optional features that can be added to the Identity Provider(IDP) are listed in the table below:
Domain Mapping
Can be used to redirect specific domain user to specific IDP
Show IdP to Users
Enable this if you want to show this IDP to all users during Login
Send Configured Attributes
Enabling this would allow you to add attributes to be sent from IDP
Select Azure Active Directory ⇒ Enterprise Applications.
Click on New Application.
Click on Non-gallery application section and enter the name for your app and click on Add button.
Click on Single sign-on from the application's left-hand navigation menu. The next screen presents the options for configuring single sign-on. Click on SAML.
Click on the edit icon to edit SAML Configuration Details
For Basic SAML configuration you need to get the Entity ID, ACS URL, and the Single Logout URL from miniOrange. Refer this step.
Enter the values in basic SAML configuration as shown in below screen
Identifier (Entity ID)
Entity ID or Issuer
Reply URL (Assertion Consumer Service URL)
ACS URL
Sign on URL (optional required during IDP-initiated SSO)
SSO Login URL
Logout URL
Single Logout URL
By default, the following Attributes will be sent in the SAML token. You can view or edit the claims sent in the SAML token to the application under the Attributes tab.
Download Federation Metadata xml, and copy the Logout URL as well. This will be used while configuring the Azure AD as IDP.
Assign users and groups to your SAML application.
As a security control, Azure AD will not issue a token allowing a user to sign in to the application unless Azure AD has granted access to the user. Users may be granted access directly, or through group membership.
Click on Users and groups from the applications left-hand navigation menu. The next screen presents the options for assigning the users/groups to the application.
After clicking on Add user, Select Users and groups in the Add Assignment screen.
The next screen presents the option for selecting user or invite an external user. Select the appropriate user and click on the Select button.
Here, you can also assign a role to this user under Select Role section.
Finally, click on Assign button to assign that user or group to the SAML application.
Step 3. Test Connection between miniOrange and Azure AD
Go to Identity Providers tab. Then click on select button under the
app you just created. Then click on Test Connection.
A new popup login window will open. Enter your credentials and login.
Now you will see TEST SUCCESSFULL in a new popup window. If not, then check if you have
missed any of the above step.
Part 3: Test Atlassian - Azure AD Configuration
Go to Atlassian Login Portal.
Enter email and click on Continue. Then you will be redirected to Azure AD Login Page.
After logging into Azure AD Login Page, you will be successfully logged into Atlassian Cloud Dashboard.
Exclusive features other miniOrange cloud app provides
Multiple Identity Providers(IDPs) to authenticate different types of users with different IDP.
Multiple Department Based Login to force the users to authenticate via a specific IDP based
on the users' department.
Domain Mapping that allow users to redirect to their IDP based on their email departments.
Custom Attribute Mapping to update the user profile attributes in the application with the user attributes
received from the IdP.
Signed Request and Response to secure your SSO with signed requests and encrypted SAML assertions.
Username Transformation to extract the required username from the received attribute using Regular Expression.
Group Mapping allows mapping user’s Identity Provider(IdP) groups to application groups. The user groups are
updated on SSO.
User Store to integrate your application with multiple user stores like AD, LDAP, external database, etc. to
easily manage your users.
Server to Cloud Migration to easily migrate your server SSO settings into Cloud.