3.2.5 Integrating Crowd with Atlassian FishEye

FishEye allows you to use Crowd to provide external authentication and authorisation.

Step 1. Configuring Crowd to talk to FishEye

Please follow the instructions in 3.2 Adding an Application.

Step 2. Configuring FishEye to talk to Crowd

Before you begin For any usernames that are already configured through the Fisheye Administration console, you will need to change the account type from 'built-in' to 'custom'. This is required for the new permissioning through Crowd to work properly.

For details please see the Fisheye documentation.

2.1 Install the Crowd Client Libraries into FishEye

Copy the Crowd integration libraries and configuration files as described in the 3.2.8 Integrating Crowd with a Custom Application documentation. This involves copying all client library JARs to the library folder of FishEye:

The version numbers have been omitted. Select the JAR which matches the name. This listing has been verified with FishEye 1.3.1.

2.2 Configure FishEye to use Crowd's Authenticator

Log in as an admin to FishEye and navigate to Users/Security. Select Setup Custom authentication and enter the following classname for the authenticator:

Leave the cache and auto-add settings to their default values. This will mean authentication calls to Crowd will be cached (improves performance) and that users will be automatically enrolled into FishEye after their initial login to FishEye via Crowd.

Fisheye requires you to pass in the configuration attributes for Crowd. Specify your configuration data, matching the values set in Step 1, through the properties editor:

2.3 Configure groups for FishEye source-repositories (if required)

If you are using any FishEye groups to control access to particular source-repositories, you will need to create the groups in Crowd and then configure FishEye as follows: 

1. In the FishEye Administration menu, select 'Global Settings', then 'Users/Security'.
2. This will display the 'Authentication Settings' screen. In the 'Permissions Summary' section, edit the 'Per-repository' field and enter the group names (separated by commas) in the 'Custom restriction' field.

Screenshot 1: 'Authentication Settings'

Screenshot 2: 'Custom Restriction'

Related Topics  

• 3.1 Using the Application Browser
• 3.2 Adding an Application
  • 3.2.1 Integrating Crowd with Apache or Subversion
  • 3.2.2 Integrating Crowd with Atlassian Bamboo
  • 3.2.3 Integrating Crowd with Atlassian Confluence
  • 3.2.4 Integrating Crowd with Atlassian CrowdID
  • 3.2.5 Integrating Crowd with Atlassian FishEye
  • 3.2.6 Integrating Crowd with Atlassian JIRA
  • 3.2.7 Integrating Crowd with Jive Forums
    • 3.2.7.1 Jive SSO
  • 3.2.8 Integrating Crowd with a Custom Application
• 3.3 Mapping a Directory to an Application
  • 3.3.1 Specifying the Directory Order for an Application
• 3.4 Specifying which Groups can access an Application
• 3.5 Specifying an Application's Address or Hostname
• 3.6 Testing a User's Login to an Application
• 3.7 Managing an Application's Session
• 3.8 Deleting or Deactivating an Application

Crowd 1.1 Documentation