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

OAuth/OpenID/OIDC Single Sign On (SSO), Discord SSO Login New Application

After clicking on the New Application button it will show you the popup for providing a name to the application. Click on the Create button after providing the application name.
Navigate to the General Information section. Copy Client ID & Client Secret.

OAuth/OpenID/OIDC Single Sign On (SSO), Discord Client ID Client Secret

Navigate to the OAuth2 section & Add Redirect button for adding the callback URL from the plugin. Once done click on the Save Changes button.

OAuth/OpenID/OIDC Single Sign On (SSO), Discord SSO Login Redirect URL

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

Select OAuth/OIDC and click on the next button.

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

Select Discord from the Selected Application dropdown menu.
Enter Client ID and Client Secret values. Use identify as scope for the first time.
This scope will not return email attribute but it is required to set username and avatar permissions in Discord. If you want email in test connection then you can use email as scope in the second time.
Click on Save button and then test connection for verifying the entered details.

SSO for JSM Customers using Discord 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?