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

Login to your Gluu Server.
Select OpenID Connect > Clients from the left-hand side menu and click on Add Client.

OAuth/OpenID/OIDC Single Sign On (SSO), Gluu Server SSO Login Add Client

Configure Standard Settings using below details.

Client Name:	Enter the client application name e.g. JIRA
Authentication method for the Token Endpoint:	Select client_secret_post from the list.
Redirect Login URI:	Enter the Callback URL provided in the plugin.
Scopes:	Select openid, profile and email from the list.
Response Type:	Select code, token and id_token.
Grant Type:	Select authorization_code from the list.
Post Logout Redirect URIs:	Enter URL where you want to redirect after Logout. e.g. JIRA Base URL.

OAuth/OpenID/OIDC Single Sign On (SSO), Gluu Server SSO Login App Settings

Once all the settings are done click on Update to save your changes.
Copy generated Client ID and Secret.
Switch to Advanced Settings for configuring Front Channel Logout URI. Enter logout URI as <Base_URL>/plugins/servlet/oauth/logout

OAuth/OpenID/OIDC Single Sign On (SSO), Gluu Server SSO Login Front Channel Logout

Click on Update to reflect your settings.
Now, we need to setup Front Channel Logout URI for oxTrust. Browse to OpenID Connect > Clients and select oxTrust Admin GUI from the clients list.

OAuth/OpenID/OIDC Single Sign On (SSO), Gluu Server SSO Login Set Logout For Oxtrust

Go to Advanced Setting section and configure Front Channel Logout URI as <Base_URL>/plugins/servlet/oauth/logout.

Note: The Front Channel Logout URI will be the same for your Atlassian app and oxTrust.

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 Gluu Server as OAuth Provider | add identity provider

Select OAuth/OIDC and click on the next button.

SSO for JSM Customers using Gluu Server as OAuth Provider | select protocol

Select Gluu Server from the Selected Application dropdown menu.
Enter Client ID, Client Secret , Gluu domain, and scope(required) as openid email profile.
Your Domain name will be https://<Gluu_Base_URL>
Click on Save button and then test connection for verifying the entered details.

SSO for JSM Customers using Gluu Server as OAuth Provider | verify 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?