Hub 2017.3 Help

Atlassian Jira Auth Module

This authentication modules lets users log in to Hub with their Jira accounts.

Enable Jira Authentication

To allow users to sign in to Hub with their Jira accounts, enable a Jira authentication module.

Prerequisites

Before you start, verify the following requirement:

  • You have Create Auth Module and Update Auth Module permissions in Hub.

Instructions

To enable the module, follow these steps.

  1. In the Access Management section of the Administration menu, select Auth Modules.
  2. From the Add Module drop-down list, select Atlassian Jira.
    • The Add Module dialog opens in the sidebar.
  3. In the Add Module dialog, enter values for the following settings:
    FieldDescription
    NameEnter a name for the authentication module.
    Server URLEnter the server address of the Jira instance. For example, http://mycompany.com/jira.
    • The Jira authentication module is created, enabled, and configured automatically.
    • The Auth Modules page displays the settings for the Jira authentication module. For additional information about the settings on this page, see the Settings section.
      jiraAuthModuleEnabled.png
    • Users can log in to Hub with their Jira credentials.

Test the Connection

To verify that the authentication module is connected to your Jira instance, test the connection.

  1. Click the Test Login button.
  2. In the Test Authentication dialog, enter the credentials of a user who is stored in your Jira instance:
    • In the Login field, enter the domainusername.
    • In the Password field, enter the password.
  3. Click the Test Login button.
    • Hub searches for the specified user account in the Jira instance. If the user is found, a success notification is displayed. If you get an error, check your user credentials and server URL.

Settings

The settings are configured automatically when the module is added to Hub. You do not have to change these settings. To configure the options that define how Hub treats new user accounts with Jira credentials, see Additional Settings.

FieldDescription
TypeDisplays the name of the application or service that is enabled for third-party authentication in Hub.
NameStores the name of the authentication module. Use this setting to distinguish this module from other authentication modules in the Auth Modules list.
Server URLStores the URL used to authenticate a login request in Hub.
Change Password URIStores the URL of the page used to manage change password requests for a Jira account.
SSL key storeSelect an uploaded SSL key store to encrypt the connection between Hub and Jira service. For more information about managing key stores in Hub, see SSL Key Stores. Also, see the Set Up SSL Keys for SAML 2.0 page: You can follow the procedure to create a key store and use it here.

Additional Settings

These settings let you manage Hub account creation and group membership, and to reduce the loss of processing resources consumed by idle connections.

OptionDescription
User creationEnables creation of Hub accounts for unregistered users who log in with an account that is stored in the connected authorization service. Hub uses the email address to determine whether the user has an existing account.
Auto-join groupsAdds users to a group when they log in with an account that is stored in the connected authorization service. You can select one or more groups. New users that auto-join a group inherit all of the permissions assigned to this group.
We recommend that you add users to at least one group. Otherwise, a new user is only granted the permissions that are currently assigned to the All Users group.
Connection timeoutSets the period of time to wait to establish a connection to the authorization service. The default setting is 5000 milliseconds (5 seconds).
Read timeoutSets the period of time to wait to read and retrieve user profile data from the authorization service. The default setting is 5000 milliseconds (5 seconds).
AuditLinks to the Audit Events page in Hub. There, you can view a list of changes that were applied to this authentication module.
Last modified: 4 October 2017