OAuth/OpenID Single Sign On (SSO) into Jira using Azure B2C

JIRA OAuth/OpenID app gives the ability to enable OAuth/OpenID Single Sign On for JIRA Software and JIRA Service Desk. JIRA Software and JIRA Service Desk are compatible with all OAuth/OpenID Providers. Here we will go through a guide to configure SSO between JIRA and Azure B2C. By the end of this guide, Azure B2C users should be able to login and register to JIRA Software and Service Desk.

Step 1: Setup Azure Active Directory B2C as OAuth Provider

  • Sign in to Azure portal.
  • Create a new tenant : You can do so by following the below given steps:
    • Click on Create a resource.
    • Search for Azure Active Directory B2C.
    • azure-ad-new-1
  • Select and scroll down until you find an option to Create a new B2C Tenant without Subscription.
  • azure-ad-new-2
  • Select Create a new Azure AD B2C Tenant and enter the following data in their respective text fields:
    • Organization name
    • Initial Domain name
    • Select your Country or Region
    • azure-ad-new-3
  • Click on the Create button.
  • Once successfully Tenant is created, you will see a message Click here, to manage your new directory click on the link for further procedure.
  • azure-ad-new-4

    If Tenant / Directory already exists then skip creating new Tenant / Directory and choose existing Directory using the below steps.

  • Else you can click on Filter icon->All Directories ->Select directory you want to logged in.
  • azure-ad-new-5
  • Now search Azure B2C in search bar and select Azure AD B2C.
  • azure-ad-new-6.png
  • Click on Applications and then on Add option to add a new application.
  • azure-ad-new-6.png
  • Configure following options to create new application.
    • Enter a name for your application under the Name text field.
    • Select Yes from the options in front of Web APP and Yes from options in front of Allow Implicit Flow.
    • Copy Callback URL from the miniOrange OAuth Client plugin (Configure OAuth tab) and save it under the Reply URL textbox.
    • Click on the Create button to create your application.
    • azure-ad-new-7
  • Click on the Applications option under the Manage Menu in the left navigation bar and you will find your application listed there. Click on your application.
  • azure-ad-new-8
  • Copy your Application ID and save it under your Client ID textbox in your miniOrange OAuth Client plugin. Then, click on the Keys option to generate a key.
  • azure-ad-new-9
  • Click on the Generate Key option and enter key name and click on the Save option.
  • azure-ad-new-10
    • It will generate a random string which you will store as Client secret in your miniOrange OAuth Client plugin.
    • azure-ad-new-11.png
  • Now, go to your dashboard and go to Azure Active Directory -> Properties. Copy the Directory ID and substitute this value whenever you need to enter Tenant ID in miniOrange OAuth Client plugin.
  • azure-ad-new-12.png

Step 2: Setup JIRA as OAuth Client

  • Enter copied Client ID, Client Secret, and Tenant ID.
  • ezgif.com-crop-16.gif
  • Add https://login.microsoftonline.com/{TENANT_ID}/oauth2/v2.0/logout?p={APP_NAME} in logout endpoint. This endpoint will logout you from Azure B2C when you logout from JIRA. logout_uri will redirect you to Jira login Page.
  • Scope is required. Configure Scope as openid.
  • Click on Test Configuration for verifying the entered details.

Step 3: User Profile

    We will be setting up user profile attributes for Jira. If your users are stored in a directory that is Read Only, please check Disable Attribute Mapping in User Profile tab and follow steps given in Matching a User.

    jira sso-14

    a. Finding correct attributes
  • Go to Configure OAuth tab. Scroll down and click on Test Configuration.
  • You will see all the values returned by your IDP to Jira in a table. If you don't see value for First Name, Last Name, Email or Username, make the required settings in your IDP to return this information.
  • Once you see all the values in Test Configuration, keep the window open and go to User Profile tab.
  • b. Setting profile attributes
  • In this tab, fill the values by matching the name of the attribute. For instance, if the Attribute Name in the Test Configuration window is NameID, enter NameID against Username
  • Setting up both Username and Email is required if you want to let users register. If you want existing users to the only login, configure the attribute using which you will match the user in Jira.
  • c. Matching a User
    When the user logs into Jira, one of the user's data/attribute coming in from the IDP is used to search the user in Jira. This is used to detect the user in Jira and log in the user to the same account.
  • Go to User Profile tab
  • Select Username or Email for Login/Search Jira user account by
  • Enter the attribute name from IDP which corresponds to Username or Email using Finding Correct Attributes

Step 4: User Groups

    We will be setting up user group attributes for Jira. If your users are stored in a directory that is Read Only, please check Disable Group Mapping in User Groups tab and skip to Setting default group.

    jira sso-15
    a. Finding Group Attribute
  • Just like we found Attribute Name for User Profile attributes, we find group attribute.
  • Go to Configure OAuth tab. Scroll down and click on Test Configuration.
  • You will see all the values returned by your IDP to Jira in a table. If you don't see value with groups, make the required settings in your IDP to return group names.
  • Once you see all the values in Test Configuration, keep the window open and go to User Groups tab.
  • Enter the Attribute Name of group against Group Attribute
  • At the bottom of the page, all groups in Jira are shown. You can map groups in IDP which correspond to Jira groups. For example, if you want all users in dev-ops and dev groups in IDP to be added to jira-users, you will need to enter dev-ops;dev against jira-users
  • If you want user mapping to work for only limited groups in Jira, check the option Update User Groups

  • b. Setting default group
  • Select the users' Default Group in the tab User Groups. If no group is mapped, users are added by default to this group.
  • You can enable default groups for all users or only new users using the option Enable Default Groups for.

Step 5: Sign In Settings

    The settings in SSO Settings tab define the user experience for Single Sign On.
    a. Sign In Settings
  • Set Enable SSO for Jira Software to allow SSO for Jira Software users.
  • Set button text for button on login page using Login Button Text
  • Set redirect URL after login using Relay State. Keep this empty for coming back to the same page user started from
  • Enable Auto-redirect to IDP if you want to allow users to login only using IDP. Enable backdoor for emergency
  • Select Secure Admin Login Options to control admin access.
  • Domain Restriction : Go to Sign In Settings, enter domain name which should be allowed for login. Eg. Allowed Domain is miniorange.com then the user with abc@miniorange.com can only able to do login.
  • jira sso-16
    b. Service Desk SSO Settings
  • Set Enable SSO For ServiceDesk Customer Portal to allow SSO for Service Desk user.
  • Set Enable SSO Only For Agents to allow SSO only for specific set of users
  • jira sso-17
    c. Sign Out Settings
    Set Logout URL or Logout Template to redirect users after logout action.

    jira sso-18

If you are looking for anything which you cannot find, please drop us an email on atlassiansupport@xecurify.com