Atlassian Cloud SSO (Single Sign-On) for PingOne using SAML
Jira SAML Single-Sign On(SSO) for Atlassian Cloud allows you to securely login using PingOne
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 PingOne as IDP
Part 1 + Part 2 : Testing SSO between Atlassian cloud as SP and PingOne 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 with PingOne
Step 1. Setup PingOne as Identity Provider
Login to your PingOne environment as the administrator. Click on your ProfileAdmin.
Go to ApplicationsAdd ApplicationNew SAML Application.
Enter the application details and click Continue. Application Name,
Application Description, and Category are required fields. For logos and
icons, PNG is the only supported graphics format.
Provide the SAML configuration details for the application.
Signing. In the dropdown list, select the signing certificate you want to use.
SAML Metadata. Click Download to retrieve the SAML metadata for Ping
One. This supplies the PingOne connection information to the application.
Protocol Version. Select the SAML protocol version appropriate for your
Upload Metadata. Click Choose File to upload the application’s metadata
file. When you are manually assigning an Entity ID value, the
Entity ID must be unique, unless you are assigning the Entity
ID value for a private, managed app (an app that is supplied & configured by PingOne for
Enterprise administrator, rather than an SP.
Single Logout Endpoint. The URL to which our service will send the SAML Single
Logout (SLO) request using the Single Logout Binding Type
that you select.
Single Logout Response Endpoint. The URL to which your service will send the SLO
Single Logout Binding Type. Select the binding type (Redirect or POST) to use for
Primary Verification Certificate. Click Choose File to upload the
primary public verification certificate to use for verifying the SP signatures on SLO
requests and responses.
Signing Algorithm. Use the default value or select the algorithm to use from the dropdown
You can also provide following optional attributes.
Encrypt Assertion. If selected, the assertions PingOne sends to the SP for the
application will be encrypted.
Encryption Certificate: Upload the certificate from miniOrange plugin to use to
encrypt the assertions.
Encryption Algorithm: Choose the algorithm to use for encrypting the
assertions. We recommend AES_256 (the default), but you can select AES_128 instead.
Transport Algorithm: The algorithm used for securely transporting the encryption
key. Currently, RSA-OAEP is the only transport algorithm supported.
Force Re-authentication. If selected, users having a current, active SSO session
will be re-authenticated by the identity bridge to establish a connection to
Click Continue to Next Step. The SSO Attribute Mapping page is displayed.
In the Attribute Mapping, Modify or add any attribute mappings as necessary for the
The summary information for the application configuration is then displayed on a new page and the new SAML
application is added to your My Applications list.
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 PingOne.
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 PingOne, 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 PingOne