Note: The configuration steps given below are applicable for the Jira versions, 1.0.0 - 1.1.53. If you want to configure SSO into WordPress using Jira for version 2.0.0+ you can find the setup steps here.
Jira SAML Single Sign-On (SSO) with WordPress as SAML IdP. Login using WordPress Users (WP as SAML IDP) plugin gives you the ability to use your WordPress (WP) credentials to login into Jira (SP). Here we will go through a
step-by-step guide to configure SSO between Jira as SP (Service Provider) and WordPress as IdP (Identity Provider).
Pre-requisites: Download And Installation
To integrate the WordPress site as an Identity Provider, you will need to install the miniOrange Login using WordPress Users ( WP as SAML IDP ) plugin:
Click on the Save button to save your configurations.
3. Attribute Mapping (This is a premium feature)
In the WordPress IDP plugin, navigate to the Attribute/Role Mapping tab.
In the User Attributes section, enter the following information and click on Save .
Click on + sign to add attributes.
User Meta Data
Click on Save.
Setting up Jira user profile attributes
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.
a. Finding correct attributes
Go to Configure IDP 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 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. You can configure it using steps given below:
Go to User Profile tab
Select Username or Email for Login/Search Jira user account by
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.
a. 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 New Users using the option.Select None if you don't want to assign any default group to SSO users. Using the option Enable Default Groups for.
b. Finding Group Attribute
Just like we found Attribute Name for User Profile attributes, we find group attribute.
Go to Configure IDP 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.
Check Disable Group Mapping option if you don't want to update groups of existing users.
c. Group Mapping
Group Mapping can be done in two ways:
Manual group mapping: If the names of groups in Jira are different than the corresponding groups in IDP, then you should use Manual group mapping.
On-The-Fly group mapping: If the names of groups in Jira and IDP are same, you should use On-The-Fly group mapping.
I. Manual Group Mapping
Check Restrict User Creation Based on Group Mapping option if you want new users to be created only if at least one of the user's IDP groups is mapped to a group in the application.
For mapping, first select a Jira group from the dropdown which lists all groups present in Jira and then enter the name of the IDP group to be mapped in the textbox beside
For example, if you want all users in 'dev' group in IDP to be added to jira-software-users, you will need to select jira-software-users from the dropdown and enter 'dev' against jira-software-users.
Use '+1' and '+10' buttons to add extra mapping fields.
Use '-' button next to each mapping to delete that mapping.
II. On-The Fly Group Mapping
Check Create New Groups option if you want new groups from IDP to be created if not found in Jira.
If the user is part of some group in Jira and that group is not present in the SAML response returned by IDP, then the user will be removed from that group in Jira.
If you don't want On-The-Fly group mapping to affect Jira groups which are managed locally then add those groups in Exclude Groups field.
4. SSO 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.
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
c. Custom Login Template
Design your own login template that will be used to intitate SSO.
d. Sign Out Settings
Set Logout URL or Logout Template to redirect users after logout action.
e. SSO Error Settings
Set error template to redirect users to a custom error page instead of login page. Use this if you have Auto-redirect to IDP enabled.
f. Advanced settings
Remember Me-cookie: If enabled, user stays logged in until user explicitly logs out.
You can extend Jira default session timeout. By default it is set to 300 mins.
Validate IDP's SAML Response: Configure time difference(in minute) here In case Jira server time is not in sync with your IDP's time.
In this Guide, you have successfully configured Jira SAML Single Sign-On (Jira SSO Login) choosing Jira as SP and WordPress as IdP using miniOrange plugin-Login using WordPress Users (WP as SAML IDP). This solution ensures that you are ready to roll out secure access to your WordPress (WP) site using Jira login credentials within minutes.
If you dont hear from us within 24 hours, please feel free to send a follow up email to firstname.lastname@example.org
This privacy statement applies to miniorange websites describing how we handle the personal
When you visit any website, it may store or retrieve the information on your browser, mostly in the
form of the cookies. This information might be about you, your preferences or your device and is
mostly used to make the site work as you expect it to. The information does not directly identify
you, but it can give you a more personalized web experience.
Click on the category headings to check how we handle the cookies.
Strictly Necessary Cookies
Necessary cookies help make a website fully usable by enabling the basic functions like site
navigation, logging in, filling forms, etc. The cookies used for the functionality do not store any
personal identifiable information. However, some parts of the website will not work properly without
These cookies only collect aggregated information about the traffic of the website including -
visitors, sources, page clicks and views, etc. This allows us to know more about our most and least
popular pages along with users' interaction on the actionable elements and hence letting us improve
the performance of our website as well as our services.