Contents

SAML SSO for JSM Customers using AWS as IDP

You can now allow External Customers to log in via SSO into Jira Service Management (previously Jira Service Desk or JSD). Integrate 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 AWS as Identity Provider

Go to AWS, search for AWS Single Sign-On in AWS Services or click on this link.
After opening the AWS SSO Service, select Enable AWS SSO.

SAML Single Sign On(SSO) using AWS Identity Provider, Enable AWS SSO

Click on Create AWS Organisation .

SAML Single Sign On(SSO) using AWS Identity Provider,Create AWS Organisation

Click on Applications → Add a new application.

SAML Single Sign On(SSO) using AWS Identity Provider,Add Application

Select Add a custom SAML 2.0 application.

SAML Single Sign On(SSO) using AWS Identity Provider, Custom Application

Fill the Details of the application.

SAML Single Sign On(SSO) using AWS Identity Provider, Details of Application

Download AWS SSO SAML Metadata file as it will be required by Service Provider in step-2.

SAML Single Sign On(SSO) using AWS Identity Provider, Download Metadata file

Go to miniorange SAML Single Sign-On Plugin → Service Provider Info tab → Download Metadata and upload it to the AWS Application Metadata section or you can copy the SP Entity ID and ACS URL from the plugin and configure endpoints manually.

SAML Single Sign On(SSO) using AWS Identity Provider, AWS Metadata

Click on Save changes and your Demo Application has been configured.
Go to Attribute Mappings configure the various attributes (first name, last name and e-mail address) for the SAML response from the Attribute mappings tab as shown:

SAML Single Sign On(SSO) using AWS Identity Provider, Attributes

Go to your configured Demo Application → Assigned users and add the users. If you want to assign new users you can navigate to the left section and go to Users→ Add User and Enter the User details and click on Next:Groups and assign group to users.

SAML Single Sign On(SSO) using AWS Identity Provider, Add User

Your user has been successfully added.

SAML Single Sign On(SSO) using AWS Identity Provider, Added User

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.