Documentation for Crowd 1.5. Documentation for other versions of Crowd is available too.
You can use Crowd to provide external authentication and authorisation for Atlassian's FishEye source-repository viewer.
Crowd supports centralised authentication and single sign-on (SSO) for FishEye versions 1.3.1 and later.
Crucible と FisheEYe
If you are using Atlassian's Crucible code review tool, you will need to follow the instructions below on integrating Crowd with FishEye. If you have the standalone version of Crucible without FishEye (available from Crucible 1.6), please follow the instructions below to set up the Crowd directory and application for Crucible instead of FishEye. If preferred, you can change the name of your Crowd application and directory to 'Crucible' rather than 'FishEye'. Then follow the further instructions to integrate Crowd with Crucible.
On this page:
CROWD
.FISHEYE
.The FishEye application will need to authenticate users against a directory configured in Crowd. You will need to set up a directory in Crowd for FishEye. For more information on how to do this, see Adding a Directory. We will assume that the directory is called FishEye Directory for the rest of this document. It is possible to assign more than one directory for an application, but for the purposes of this example, we will use FishEye Directory to house FishEye users.
If you wish to use Crowd groups to control access to your FishEye repositories, you should set up your groups in Crowd. See the documentation on Creating Groups for more information on how to define these groups.
Use Crowd to create at least one user in the FishEye Directory. If you are using groups, assign your user(s) to the appropriate groups. The Crowd documentation has more information on creating users and assigning users to groups.
Crowd needs to be aware that the FishEye application will be making authentication requests to Crowd. We need to add the FishEye application to Crowd and map it to the FishEye Directory:
属性 |
説明 |
---|---|
名前 |
The username which the application will use when it authenticates against the Crowd framework as a client. This value must be unique, i.e. it cannot be used by more than one application client. |
説明 |
A short description of the application. Note: A web URL is often helpful. |
アクティブ |
Only deselect this if you wish to prevent all users (from all directories) from accessing this application. |
パスワード |
The password which the application will use when it authenticates against the Crowd framework as a client. |
Confirm Password |
Retype the same password as above, to confirm it. |
Default Directory |
A directory that contains relevant users. Note: Additional directories can be added later. |
Now that Crowd is aware of the FishEye application, Crowd needs to know which users can authenticate (log in) to FishEye via Crowd. You can either allow entire directories to authenticate, or just particular groups within the directories. In our example, we will allow the entire FishEye Directory to authenticate:
If you wish to authorise specific groups only, please see Mapping a Directory to an Application and Specifying which Groups can access an Application.
Please see Specifying an Application's Address or Hostname. Please note:
localhost
.localhost
is a permissible foreign host. However, you will also need to manually add the IP address 127.0.0.1
, as incoming requests to Crowd from FishEye (both on the same, local, host) may be from the host 127.0.0.1
and not localhost
. Crowd does not do a DNS lookup of the hostname. Rather, it compares the values as is. Ensure the "Status" field is set to "true". The instructions below are for FishEye 1.4.x and later. If you are using FishEye 1.3.x, please follow the guide for earlier versions of FishEye.
If you have an existing FishEye installation with existing built-in users, please do the following for each username in FishEye:
http://localhost:8095/crowd/services/
crowd.token
cookies. This is useful in environments where you want FishEye to ignore crowd.token
cookies set by other Crowd-enabled applications.
For more information, please see the Fisheye documentation on configuring external authentication sources.
If you have created groups in the Crowd directory which is mapped to your FishEye application (see Step 1 above), the Crowd groups can be seen in FishEye. Now you can set up group authorisation for your FishEye repositories.
Allow the groups to access your FishEye repositories as follows:
Screenshot 1: 'Authentication Settings'
Screenshot 2: 'Edit Security'
If you are using Atlassian's Crucible code review tool, please take a look at the further instructions on integrating Crowd with Crucible.