Doc downloads (PDF, HTML & XML)
[FishEye Knowledge Base]
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:
You need to be an administrator in JIRA and a system administrator in FishEye to perform the following tasks.
192.168.10.12
.192.168.10.1/16
. For more information, see the introduction to CIDR notation on Wikipedia and RFC 4632.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:
Setting | Description |
---|---|
Name | A meaningful name that will help you to identify this Jira server in the list of directory servers. Examples:
|
Server URL | The web address of your Jira server. Examples:
|
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. |
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. |
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. |