Contents

SAML SSO for JSM Customers using JumpCloud as IDP

You can now allow External Customers to login into Jira Service Management (previously Jira Service Desk or JSD) via SSO! Integration with various customer portals like Atlassian Service Management and access tickets with the help of SAML SSO for JSM Customers.

Download And Installation

Log into your Jira instance as an admin.
Navigate to the settings and Click on Apps.
Locate SAML SSO for JSM Customers.
Click on free trial to begin a new trial SAML SSO for JSM Customers.
On menu bar click on Apps. Locate SAML SSO for JSM Customers .

Step 1: Setup JumpCloud as Identity Provider

SAML Single Sign-On (SSO) using JumpCloud (IdP),login page

Go to SSO tab and click on + icon given on the page for adding a new SSO app.

SAML Single Sign-On (SSO) using JumpCloud (IdP), new SSO

Click on the Custom SAML App button.

SAML Single Sign-On (SSO) using JumpCloud (IdP), Custom App

On the New Application page, provide a name and description (optional) for your app and then go to the SSO tab.

Step 1.1: Import SP Metadata

Enter details manually from the SP Information tab.

SAML Single Sign-On (SSO) using JumpCloud (IdP), JumpCloud-Manual Configuration

Fields to be filled in JumpCloud	Corresponding details to be copied from the plugin
IdP Entity ID	Enter a unique IdP Entity ID of your choice
SP Entity ID	SP Entity ID/ Issuer
ACS URL	ACS URL
SP Certificate	Certificate (Download the file and upload here)

Step 1.2: Attribute Mapping

Scroll down to the Attributes section and click the add attribute button.
In the left-side input field provide Attribute Name to be sent in SAML assertion and, select the appropriate attribute value from the dropdown given on the right side.
For example, below we have provided userName as attribute and selected username from the dropdown. Similarly add all the attributes you wish to provision to service provider.

SAML Single Sign-On (SSO) using JumpCloud (IdP), Attribute Mapping

Step 1.3: Group Mapping

In the Group Attributes section enable the checkbox and provide the group attribute name.

SAML Single Sign-On (SSO) using JumpCloud (IdP), Group Mapping

Go to the User Groups tab. Here you can select which groups will have access to this SSO app. This is an important step to allow users to perform SSO with JumpCloud.

Click on the activate button given at the bottom and then click on Continue in the confirmation dialog box.
On the SSO page, select the checkbox given in front of the newly created application and click on the export metadata button. IDP metadata file will be downloaded.

SAML Single Sign-On (SSO) using JumpCloud (IdP), Export Metadata

Step 2. Setup JSM as Service provider

Go to the Manage Apps -> click Getting started under SSO Integration with Helpdesk then click on the Add New Identity Provider.

SSO for JSM Customers using ADFS as OAuth Provider | add identity provider

Select SAML and click on the next button.

SSO for JSM Customers using ADFS as OAuth Provider | select protocol

A. By Metadata URL :

Click on Import IDP Metadata.

SAML Single Sign On (SSO) using Okta Identity Provider, Okta SSO Login,IDP Metadata Link

Enter IDP name.
Choose IDP metadata URL / File: Enter your metadata URL / File
Click Import

B. Manual Configuration :

To configure the IDP manually, you will need to have the following details from your IDP's metadata.

IDP Entity ID
Single Sign On URL
Single Logout URL
X.509 Certificate

Once you have added the IDP metadata, click on Save. If the IDP has been added successfully, Click on the Test Configuration button to test if the IDP was added successfully.

Step 3: Integrate Atlassian HelpDesk with JSM SSO

Click on the Configure API Token and configure the Service Account API token with the email.

It is necessary to have admin permissions for the service account.

After successful configuration of API token all the service desk projects with respective links will be displayed. These substituted links will be used by customers for accessing particular projects with SSO.

Copy any of the substitute links you see for your portals and try accessing it in a private browser window. You would be automatically redirected to your Identity Provider for authentication and would be allowed access to the portal only after successful authentication.