SSO for JSM Customers using Microsoft Entra ID (Previously known as Azure AD) as OAuth Provider

Our SAML/OAuth SSO for JSM Customers app offers the functionality to seamlessly integrate OAuth/OpenID Single Sign-On into the JSM customer portal, ensuring compatibility with all OAuth/OpenID Providers. This guide will outline the steps for configuring SSO between the JSM customer portal and your OAuth/OpenID Provider. By following these instructions, customers will undergo authentication via your OAuth/OpenID Provider prior to accessing the JSM customer portal. This integration facilitates a smooth customer experience while also mitigating spam ticket.

Try it for free

Download and Installation

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

Step 1: Set Up Azure AD as OAuth Provider

Sign in to Azure portal.
Click on view Manage Azure Active Directory.

OAuth/OpenID/OIDC Single Sign On (SSO), Microsoft Entra ID (Previously known as Azure AD) SSO Login

In the left-hand navigation pane, click the App registrations service, and click New registration.

OAuth/OpenID/OIDC Single Sign On (SSO), Microsoft Entra ID (Previously known as Azure AD) SSO App-Registration

When the Create page appears, enter your application's registration information.
In the Redirect URI enter the Callback URL from the plugin. eg: [application-base-url]/plugins/servlet/oauth/callback

OAuth/OpenID/OIDC Single Sign On (SSO), Microsoft Entra ID (Previously known as Azure AD) SSO registration

When finished, click Register. Microsoft Entra ID (Previously known as Azure AD) assigns a unique Application ID to your application. Copy Application ID and the Directory ID , this will be your Client ID and Tenent ID respectively.

OAuth/OpenID/OIDC Single Sign On (SSO), Microsoft Entra ID (Previously known as Azure AD) SSO Overview

Go to Certificates and Secrets from the left navigaton pane and click on New Client Secret. Enter description and expiration time and click on Add option.

OAuth/OpenID/OIDC Single Sign On (SSO), Microsoft Entra ID (Previously known as Azure AD) SSO secret-Key

Copy Value. This will be your Client Secret.

OAuth/OpenID/OIDC Single Sign On (SSO), Microsoft Entra ID (Previously known as Azure AD) SSO Secret-Key-2

Step 2: Setup JSM as OAuth Client

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 Microsoft Entra ID (Previously known as Azure AD) as OAuth Provider | add identity provider

Select OAuth/OIDC and click on the next button.

SSO for JSM Customers using Microsoft Entra ID (Previously known as Azure AD) as OAuth Provider | Select provider

Select Microsoft Entra ID (Previously known as Azure AD) from the Selected Application dropdown menu.
Enter Client ID, Client Secret, Tenant ID in the given field.
Configure scope as User.Read and for fetching group info use scope Directory.read.all.
Click on Save button and then test connection for verifying the entered details.

SSO for JSM Customers using Azure AD as OAuth Provider | Enter details

Step 3: User Attribute Mapping

For filtering users, navigate to the Manage Users tab, where you will find filter users by section.

Once you see all the values in Test connection, go to User Attribute Mapping. Map attributes like Email, firstname, lastname, etc. Click on Save.

SSO for JSM Customers using Azure AD as OAuth Provider | attribute mapping

Step 4: Integrate Atlassian HelpDesk with JSM SSO

Navigate to the Jira Configuration tab. 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.

SSO for JSM Customers using ADFS as OAuth Provider | 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.

SSO for JSM Customers using ADFS as OAuth Provider | API token

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.

Additional Resources

Did this page help you?