Atlassian Cloud SSO (Single Sign-On) for WSO2 using SAML
Jira SAML Single-Sign On(SSO) for Atlassian Cloud allows you to securely login using WSO2
credentials. Single Sign-on (SSO) into your Atlassian
Access or Atlassian Jira SAML 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
1. Atlassian Access Subscription
Atlassian Access is an additional subscription applied across the Atlassian cloud products like Jira
Software, Jira Service Management, Jira Work Management, Confluence, Bitbucket, etc. So it is needed for
Single Sign-On(SSO) or any Cloud Service which comes under Atlassian Access.
2. Domain Verification:
The first step of Atlassian Access starts with the Domain Verification Process to enforce SAML 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.
In this document, we will demonstrate the setup in two parts.
Part 1: Configure SAML SSO between Atlassian cloud as SP and miniOrange as IDP
Part 2: Configure SAML SSO between miniOrange as SP and WSO2 as IDP
Part 1 + Part 2 : Testing SSO between Atlassian cloud as SP and WSO2 as IDP
using miniOrange Identity Broker.
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
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
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.
do not have any IDP, you can always go with miniOrange IDP.
Part 2: Setup miniOrange
Step 1. Setup WSO2 as Identity Provider
Login to your WSO2 admin console.
Select Add under the Service Providers tab.
Select mode as Manual Configuration.
Enter the Service Provider Name and click on Register button.
Select Upload SP certificate option under SP Certificate Type.
Copy the certificate from plugin and provide it into Application Certificate field.
You can also download the certificate file and upload it through Browse file option.
Under Claim Configuration, select Use Local Claim Dialect.
For Requested Claims, add http://wso2.org/claims/emailaddress as a claim URI.
Set Subject Claim URI to http://wso2.org/claims/nickname.
Under Inbound Authentication Configuration > SAML2 Web SSO Configuration, click
Enter Issuer value as provided under the Service Provider Info tab of the plugin.
Enter Assertion Consumer URL (ACS) as provided under Service Provider Info tab and
click on Add.
Check Enable Response Signing.
Check the Enable Attribute Profile and include attributes in the response always.
Check the Enable Audience Restriction.
Enter the Audience URL value provided under Service
Provider Info tab of plugin and click on Add.
Check the Enable Recipient Validation. Enter the Recipient URL value provided
under Service Provider Info tab of plugin and click on Add.
Click on Download IDP Metadata button save the IDP metadata file.
Click on Register to save the configuration.
Click on Update on Service Providers page to save the configuration.
Select Resident under Identity Providers tab from the menu.
Enter Home Realm Identifier value that you want (usually your WSO2 server address).
From the left navigation bar select Identity Provider. Then click on Add Identity
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 WSO2.
Click on Show Metadata details under For SP - INITIATED
either manually enter details or use Metadata URL or File
Now to create SAML app for WSO2, go to the Add Identity Provider page and click on
Import IDP Metadata.
Import the metadata file that you will get from the SAML Login Information section of
If you don't have a metadata file, you can also provide the details manually. You need to configure
IDP Entity ID
Entity ID of IDP
Single Login URL
Login Url from IDP
Single Logout URL
Logout Url from IDP
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:
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
Click on Save.
Step 3. Test connection between miniOrange and WSO2