SAML Single Sign-On for Jira — Integration with AuthPoint

Deployment Overview

This document describes how to set up multi-factor authentication (MFA) for SAML Single Sign-On for Jira with AuthPoint as an identity provider.

SAML Single Sign-On for Jira is an app on the Atlassian Jira Software Server (On-Premises). SAML Single Sign-On for Jira and the Jira Software Server must already be configured and deployed before you set up MFA with AuthPoint.

SAML Single Sign-On for Jira Authentication Data Flow with AuthPoint

AuthPoint communicates with various cloud-based services and service providers with the SAML protocol. This diagram shows the data flow of an MFA transaction for SAML Single Sign-On for Jira.

Before You Begin

Before you begin these procedures, make sure that:

• End users can log in to the Jira Software.
• An AuthPoint user has an assigned token.
• You have an AuthPoint identity provider (IdP) certificateAn AuthPoint IdP certificate is required for SAML authentication. (see Certificate Management).

Configure SAML Single Sign-On for Jira

You must first download the metadata file from the Resources page in the AuthPoint management UI. When you have the metadata file, you can configure SAML Single Sign-On for Jira.

To download the metadata file:

1. Log in to WatchGuard Cloud.
2. Click Configure > AuthPoint.
   If you have a Service Provider account, pivot to Subscriber view.
3. From the navigation menu, select Resources.
   The Resources page appears.
4. Click Certificate.

5. Next to the AuthPoint certificate you want to associate with your resource, click and select Download Metadata.

   We recommend that you choose the certificate with the latest expiration date. For more information, see Certificate Management.

   The AuthPoint metadata provides SAML Single Sign-On for Jira with the information necessary to identify AuthPoint as a trusted identity provider.

To install and configure SAML Single Sign-On for Jira:

1. Log in to the Jira Software Server.
2. Click the administration menu () and select Manage apps.
3. Click Find new apps.
4. Search and install SAML Single Sign-On for Jira.

To install and configure AuthPoint as the SAML identity provider:

1. From the navigation menu, select SAML Single Sign-On.
2. On the SAML Single Sign-On Plugin Configuration page, select Identity Providers.
3. Click Add IdP.

4. From the IdP Type drop-down list, select Other SAML Identity Provider.
5. In the Name text box, type AuthPoint.

6. Click Next.
7. Download SAML Single Sign-On Metadata via the Metadata URL.

8. Click Next.
9. From the Metadata Upload drop-down list, select I have a metadata XML file.
10. Click Select metadata XML file and select the AuthPoint metadata file you downloaded.

11. Click Import.
12. Click Next.
13. On the User ID Attribute and Transformation page, from the Authentication Attribute drop-down list, select Email.

14. Click Next.
15. On the User Creation and Update page, from the User Update Method drop-down list, select No User update.

16. Click Save & Next.

To test the new configuration:

1. Click Start test when you have finished the AuthPoint configuration.
   You can also click Skip test & configure manually.

2. When the test status is Success, click Next.

3. Select the Enable SSO Redirect check box and click Save & Close.

4. From the navigation menu, select SAML Single Sign-On > IdP Selection.
5. In the IdP Selection Method list, select Email Address.
6. In the Email domains section, click Add one.

7. Enter an email domain to bind with an IdP. In this example, we enter watchguard\.com.

8. Click Save settings.

Configure AuthPoint

Before AuthPoint can receive authentication requests from SAML Single Sign-On for Jira, you must:

• Specify the SAML Single Sign-On for Jira client as a SAML resourceIn AuthPoint, resources are the applications and services that your users connect to. in AuthPoint.
• Add an access policyAccess policies specify which resources users in a group can authenticate to and which authentication methods they can use. for the SAML Single Sign-On for Jira resource to the user group(s) that must authenticate to log in.

Add a SAML Single Sign-On for Jira Resource

From the AuthPoint management UI:

1. From the navigation menu, select Resources.
2. From the Choose a Resource Type drop-down list, select SAML. Click Add Resource.

3. On the SAML page, in the Name text box, type a name for this resource.
4. From the Application Type drop-down list, select Others.
5. In the Service Provider Entity ID text box, type the entityID value from the Single Sign-On for Jira metadata file.
6. In the Assertion Consumer Service text box, type the AssertionConsumerService Location value from the Single Sign-On for Jira metadata file.
7. From the User ID sent on redirection to service provider drop-down list, select Email.
8. From the Signature Method drop-down list, select SHA-256.
9. From the AuthPoint Certificate drop-down list, select the certificate to associate with your resource.

   We recommend that you choose the certificate with the latest expiration date. For more information, see Certificate Management.

10. Click Save.

Add an Access Policy to AuthPoint

You must have at least one user group in AuthPoint for authentication with Jira, and you must assign an access policy for the Jira resource to that group. If you already have a group, you do not need to add another group.

In the AuthPoint management UI:

1. From the navigation menu, select Groups.
2. To add a new group, click Add Group. If you already have a group that you want to use, select the group to edit it.

3. In the Name text box, type a descriptive name for the group.
4. (Optional) In the Description text box, type a description of the group.

5. In the Access Policy section, click Add Policy.

6. In the Add Policy dialog box, from the Resource drop-down list, select the resource you want to add an access policy for.
7. (Optional) To require that users type their password before they authenticate for this resource, select the Require Password Authentication slider.
8. Select the authentication options that users in this group can choose from when they authenticate.

   For SAML resources, if you select more than one authentication option, users must choose one of the available options when they authenticate. For example, if you select OTP and Push, users can choose to type their OTP or approve a push to authenticate. You cannot require that they do both.

9. Click Add.

10. (Optional) Add one or more safe locations to your group. For more information about safe locations and detailed instructions to add them, see About Safe Locations.
11. Click Save.

Before you assign users to a group, you must add them to AuthPoint. You can manually add user accounts or import user accounts from your LDAP database. For more information on how to add user accounts, see Add User Accounts.

Test the Integration

To test the integration of AuthPoint and your Single Sign-On for Jira, you can authenticate with a mobile token on your mobile device. You can choose any authentication method (for example, one-time password, QR code, or push).

In this example, we show the push authentication method. Users receive a push notification in the mobile app that they must approve to authenticate.

The email address used in this procedure must be associated with both your AuthPoint and Jira user accounts.

To test the integration:

1. In a web browser, go to the Jira login URL (for example, http://xxxxxxxx:8080).

2. In the text box, type the user email address.
   The AuthPoint authentication page appears.
3. Type the same email address and click Next.
4. If required, in the Password text box, type your password.
5. For the authentication method, click Send Push.
6. Approve the authentication request that is sent to your mobile device.
   The Jira dashboard appears.

Give Us Feedback  ●   Get Support  ●   All Product Documentation  ●   Technical Search

© 2019 WatchGuard Technologies, Inc. All rights reserved. WatchGuard, the WatchGuard logo, and Firebox are trademarks or registered trademarks of WatchGuard Technologies, Inc. in the United States and/or other countries. All other tradenames are the property of their respective owners.