Connecting to JIRA for user management

(warning)  This page does not apply to JIRA Cloud; you can't use JIRA Software Cloud to manage your FishEye users.

You can connect FishEye to an existing Atlassian JIRA instance to delegate FishEye user and group management, and authentication. FishEye provides a "read-only" connection to JIRA for user management. This means that users and groups, fetched from JIRA, can only be modified or updated in that JIRA server, rather than in FishEye.

Choose this option, as an alternative to Atlassian Crowd, for simple configurations with a limited number of users. Note that FishEye can only connect to an instance running JIRA 4.3 or later.

Connecting FishEye and JIRA is a 3-step process:

1. Set up JIRA to allow connections from FishEye

2. Set up FishEye to connect to JIRA Software

3. Set up FishEye users and groups in JIRA Software

Also on this page:

(warning) You need to be an administrator in JIRA and a system administrator in FishEye to perform the following tasks.

1. Setup JIRA to allow connections from FishEye 

  1. Log in as a user with the 'JIRA Administrators' global permission.
  2. For JIRA 4.3.x, select Other Application from the 'Users, Groups & Roles' section of the 'Administration' menu.
    For later versions, choose Administration > User management > JIRA User Server.
  3. Click Add Application.
  4. Enter the application name (case-sensitive) and password that FishEye will use when accessing JIRA Software.
  5. Enter the IP address of your FishEye instance. Valid values are: 
    • A full IP address, e.g. 192.168.10.12.
    • A wildcard IP range, using CIDR notation, e.g. 192.168.10.1/16. For more information, see the introduction to CIDR notation on Wikipedia and RFC 4632.
  6. Click Save.
  7. Define the directory order, on the 'User Directories' screen, by clicking the blue up- and down-arrows next to each directory. The directory order has the following effects:
    • The order of the directories is the order in which they will be searched for users and groups.
    • Changes to users and groups will be made only in the first directory where the application has permission to make changes.

2. Setup FishEye to connect to JIRA

  1. Log in to FishEye as a user with 'Admin' permission.
  2. In the FishEye administration area click User Directories (under 'Accounts').
  3. Click Add Directory and select Atlassian JIRA.
  4. Enter settings, as described below.
  5. Test and save the directory settings.
  6. Define the directory order, on the 'User Directories' screen, by clicking the arrows for each directory. The directory order has the following effects:
    • The order of the directories is the order in which they will be searched for users and groups.
    • Changes to users and groups will be made only in the first directory where the application has permission to make changes.

3. Set up FishEye users and groups in JIRA

In order to use FishEye, users must be a member of a group that has the 'Access to FishEye' global permission. Follow these steps to configure your FishEye groups in JIRA:

  1. Add a group for FishEye users in JIRA.
  2. Add your own username as a member of the above group..
  3. Log in to FishEye using and go to the administration area. Click Global Permissions (under 'Security Settings'). Assign the appropriate permissions to the JIRA group. See Global permissions.

Server settings

Setting

Description

Name

A meaningful name that will help you to identify this JIRA server in the list of directory servers. Examples:

  • JIRA Service Desk Server
  • My Company JIRA

Server URL

The web address of your JIRA server. Examples:

  • http://www.example.com:8080
  • http://jira.example.com

Application Name

The name used by your application when accessing the JIRA server that acts as user manager. Note that you will also need to define your application to that JIRA server, via the 'Other Applications' option in the 'Users, Groups & Roles' section of the 'Administration' menu.

Application Password

The password used by your application when accessing the JIRA server that acts as user manager.

JIRA server permissions

Setting

Description

Read Only

The users, groups and memberships in this directory are retrieved from the JIRA server that is acting as user manager. They can only be modified via that JIRA server.

Advanced settings

Setting

Description

Enable Nested Groups

Enable or disable support for nested groups. Before enabling nested groups, please check to see if nested groups are enabled on the JIRA server that is acting as user manager. When nested groups are enabled, you can define a group as a member of another group. If you are using groups to manage permissions, you can create nested groups to allow inheritance of permissions from one group to its sub-groups.

Enable Incremental Synchronization Enable or disable incremental synchronization. Only changes since the last synchronization will be retrieved when synchronizing a directory.

Synchronization Interval (minutes)

Synchronization is the process by which the application updates its internal store of user data to agree with the data on the directory server. The application will send a request to your directory server every x minutes, where 'x' is the number specified here. The default value is 60 minutes.

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport