SSO for JSM Customers using GitLab 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.


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: Setup GitLab as OAuth Provider

  • Login to Gitlab : Go to GitLab or your on-premise GitLab Server and login to your account.
  • Navigate to your profile settings.
    • OAuth/OpenID/OIDC Single Sign On (SSO), GitLab SSO Login Setup Gitlab
  • Create app : Select applications in left menu.
    • OAuth/OpenID/OIDC Single Sign On (SSO), GitLab SSO Login Create app
  • Provide the required details.
    • Name : This can be anything. Consider something like <Organization>'s GitLab or <Your Name>'s GitLab or something else descriptive.
    Redirect URI : Copy Callback URL from plugin.
    OAuth/OpenID/OIDC Single Sign On (SSO), GitLab SSO Login Redirect URI

    NOTE: The check-box for “api” needs to be checked, as it’s unchecked by default.

  • Get Client ID & Client Secret : Copy Application Id , Secret and Scope.
    • OAuth/OpenID/OIDC Single Sign On (SSO), GitLab SSO Login Get Client ID

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 GitLab as OAuth Provider | add identity provider
  • Select OAuth/OIDC and click on the next button.
    • SSO for JSM Customers using GitLab as OAuth Provider | select protocol
  • Select GitLab from the Selected Application dropdown menu.
  • Use Application ID for Client ID, and Secret for Client Secret.
  • Configure scope as “api”.
  • In case of Self Hosted GitLab server, provide a complete domain URL. e.g <https://gitlab-domain.com>.
  • Click on Save button and then test connection for verifying the entered details.
    • SSO for JSM Customers using GitLab as OAuth Provider | verify details

Step 3: User Attribute Mapping

  • 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 GitLab 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.



Free Trial

If you don't find what you are looking for, please contact us at support-atlassian@miniorange.atlassian.net or raise a support ticket here.