273
Customers have installed this app in at least 273 active instances.
Get it nowFree app

Easily configure JIRA to support SAML 2.0

Easily configure JIRA to support SAML 2.0

Quick Setup

Simple UI for End Users

Flexible

Easily configure Confluence to work with your Identity Provider

Once the plugin is configured, the end user experience is easy to understand.

The plugin can be configured to either force Single-Sign-On through your IdP or to allow the user to choose SAML or username/password.

More details

We hope you enjoy using the SAML 2.0 Single Sign-On for JIRA plugin. If you run into any issues, please use the Github issue tracker or look through the wiki for additional information on configuring the plugin - links for both can be found under the "support" tab.

Reviews for cloud

(6)
Sign in to write a review
by Steve Tyler on 2017-09-22
Very little documentation, no support, multiple bugs, returns a 500 error when trying to configure for JIRA. Confluence integration is functional if you can figure out what info to supply.
Was this review helpful?YesNo
by May Srichainont on 2016-06-15
This question is to Tobias, may I ask how you able to work thru the issue you mentioned where you've enable 'Force SSO' and afterward you cannot access the admin realm anymore and end up in a redirection loop to the standard page. How are you able to workaround this? Thank you.
1 out of 1 found this review helpful
Was this review helpful?YesNo
by Tobias Spöcker on 2016-04-20
Be very careful with "force SSO"!! We tested evrything and it seemed to work. So we enabled that feature... BUT then you cannot access the admin realm anymore! You always end up in a redirection loop to the standard page. This bug was already reported several times and no reaction seen so far. The rest works as expected. But the setup is for nox experienced people a bit difficult.
1 out of 1 found this review helpful
Was this review helpful?YesNo
by Jouko Markkanen on 2016-03-08
Works fine, but I agree on weaton's comment on the lacking documentation. We use this together with Microsoft AD FS as identity provider. Had to set up using some random values as Entry ID in the plugin and the identifier to configure in AD FS, then try to log in and read the correct values from the logs in both ends. To help other users, the values would be "https://jira.example.com:443/jiraSAML" for the identifier configured in AD FS, and "http://adfs.example.com/adfs/services/trust" as Entity ID in the plugin config form, login URL would be "https://adfs.example.com/adfs/ls", and in the certificate field copy/paste the Token signing certificate (base64 encoded) from the AD FS server. Finally, configure a claim rule in AD FS to map SAM-Account-Name into the Name ID field of the outgoing claim, if you use LDAP/AD synchronization in Jira. One mysterious thing is that the "Use Corporate Login" button that is shown in the Jira login page is not always visible on the login form of the default Jira dashboard. Haven't figured out yet why, and why it occasionally appears there.
2 out of 2 found this review helpful
Was this review helpful?YesNo
by Robert Heckel on 2016-02-04
No longer is able to create a user in 7.0.10 due to the use of deprecated class: com.atlassian.jira.user.util.UserUtil.createUserNoNotification Setup was pretty straight forward. Functioned better than similar paid versions tested, until the above occurred.
0 out of 1 found this review helpful
Was this review helpful?YesNo

Reviews for server

(6)
Sign in to write a review
by Steve Tyler on 2017-09-22
Very little documentation, no support, multiple bugs, returns a 500 error when trying to configure for JIRA. Confluence integration is functional if you can figure out what info to supply.
Was this review helpful?YesNo
by May Srichainont on 2016-06-15
This question is to Tobias, may I ask how you able to work thru the issue you mentioned where you've enable 'Force SSO' and afterward you cannot access the admin realm anymore and end up in a redirection loop to the standard page. How are you able to workaround this? Thank you.
1 out of 1 found this review helpful
Was this review helpful?YesNo
by Tobias Spöcker on 2016-04-20
Be very careful with "force SSO"!! We tested evrything and it seemed to work. So we enabled that feature... BUT then you cannot access the admin realm anymore! You always end up in a redirection loop to the standard page. This bug was already reported several times and no reaction seen so far. The rest works as expected. But the setup is for nox experienced people a bit difficult.
1 out of 1 found this review helpful
Was this review helpful?YesNo
by Jouko Markkanen on 2016-03-08
Works fine, but I agree on weaton's comment on the lacking documentation. We use this together with Microsoft AD FS as identity provider. Had to set up using some random values as Entry ID in the plugin and the identifier to configure in AD FS, then try to log in and read the correct values from the logs in both ends. To help other users, the values would be "https://jira.example.com:443/jiraSAML" for the identifier configured in AD FS, and "http://adfs.example.com/adfs/services/trust" as Entity ID in the plugin config form, login URL would be "https://adfs.example.com/adfs/ls", and in the certificate field copy/paste the Token signing certificate (base64 encoded) from the AD FS server. Finally, configure a claim rule in AD FS to map SAM-Account-Name into the Name ID field of the outgoing claim, if you use LDAP/AD synchronization in Jira. One mysterious thing is that the "Use Corporate Login" button that is shown in the Jira login page is not always visible on the login form of the default Jira dashboard. Haven't figured out yet why, and why it occasionally appears there.
2 out of 2 found this review helpful
Was this review helpful?YesNo
by Robert Heckel on 2016-02-04
No longer is able to create a user in 7.0.10 due to the use of deprecated class: com.atlassian.jira.user.util.UserUtil.createUserNoNotification Setup was pretty straight forward. Functioned better than similar paid versions tested, until the above occurred.
0 out of 1 found this review helpful
Was this review helpful?YesNo

Pricing

Basic support resources are available for this app.

Vendor support resources

Documentation

Find out how this app works.

Community

Community discussions connect you to the vendor and other customers who use this app.

See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community

Atlassian-hosted discussions connect you to other customers who use this app.

Versions

Version 1.0.5 JIRA Server 6.0 - 7.4.4 Released 2017-03-28

Summary

Bug fixes for Jira 7.2.x

Details

fix for https://github.com/bitium/jira-saml-plugin/issues/46

Installation

  1. Log into your JIRA instance as an admin.
  2. Click the admin dropdown and choose Add-ons. The Manage add-ons screen loads.
  3. Click Find new add-ons from the left-hand side of the page.
  4. Locate SAML 2.0 Single Sign-On for JIRA via search. Results include app versions compatible with your JIRA instance.
  5. Click Install to download and install your app.
  6. You're all set! Click Close in the Installed and ready to go dialog.

To find older SAML 2.0 Single Sign-On for JIRA versions compatible with your instance, you can look through our version history page.

Similar apps