外部ユーザー ディレクトリ
You can connect Fisheye to external user directories. This allows you to use existing users and groups stored in an enterprise directory, and to manage those users and groups in one place.
ユーザー管理機能には以下が含まれます。
- Authentication: determining which user identity is sending a request to Fisheye.
- 認可: 認証されたユーザーのアクセス権限を決定します。
- ユーザー管理: ユーザーのアカウントのプロファイル情報を保持します。
- グループ メンバーシップ: グループおよびグループ メンバーシップを格納および取得します。
これらはユーザー管理システムの個別のコンポーネントであることを理解することが重要です。上記のタスクのいずれかまたはすべてのために外部ディレクトリを使用できます。
There are several approaches to consider when using external user directories wth Fisheye, described briefly below:
- Fisheye provides a "read-only" connection to external directories for user management. This means that users and groups, fetched from any external directory, can only be modified or updated in the external directory itself, rather than in Fisheye.
- Connecting Fisheye to your external directory is not sufficient to allow your users to log in to Fisheye. You must explicitly grant them access to Fisheye in the global permission screen.
- Fisheye comes with an internal user directory, already built-in, that is enabled by default at installation.
ライセンスの考慮事項
When connecting Fisheye to an external directory, be careful not to allow access to Fisheye by more users than your Fisheye license allows. If the license limit is exceeded, users will not be able to use the application and Fisheye will display a warning banner. You can manage which users have access to Fisheye, using the global permission screen.
LDAP
ユーザーおよびグループがエンタープライズ ディレクトリに保存されている場合、LDAP ディレクトリ サーバーに接続することを検討する必要があります。
There are two common ways of using an external LDAP directory with Fisheye:
- For full user and group management, including for user authentication — see Connecting to an existing LDAP directory for instructions.
- For delegated user authentication only, while using Fisheye's internal directory for user and group management — see Delegating authentication to an LDAP directory for instructions.
Fisheye is able to connect to the following LDAP directory servers:
- Microsoft Active Directory
- Apache Directory Server (ApacheDS) 1.0.x および 1.5.x
- Apple Open Directory (読み取り専用)
- Fedora Directory Server (読み取り専用 Posix Schema)
- Novell eDirectory サーバ
- OpenDS
- OpenLDAP
- Open LDAP (読み取り専用 Posix Schema)
- Generic Posix/RFC2307 ディレクトリ (読み取り専用)
- Sun Directory Server Enterprise Edition (DSEE)
- 任意の汎用 LDAP ディレクトリ サーバー
Jira アプリケーション
You can delegate Fisheye user and group management, as well as user authentication, to a Jira application. This is a good option if you already use a Jira application in your organization. Note that Fisheye can only connect to a Jira application server running Jira 4.3 or later.
You should consider using Atlassian Crowd for more complex configurations with a large number of users.
See Connecting to Jira for user management for configuration instructions.
Crowd
You can connect Fisheye to Atlassian Crowd for user and group management, as well as for user authentication.
Crowd は、Web ベースのアプリケーションの認証と認可を処理するアプリケーション セキュリティ フレームワークです。Crowd を使用することによって、シングル サインオン (SSO) と中央での ID 管理がサポートされ、複数の Web アプリケーションを複数のユーザー ディレクトリと統合できます。Crowd 管理ガイドを参照してください。
Crowd を使用して複数のディレクトリ タイプで既存のユーザーおよびグループを管理する場合や、他の Web ベースのアプリケーションのユーザーが存在する場合は、Crowd に接続することを検討することをおすすめします。
See Connecting to Crowd for configuration instructions.
複数のディレクトリ
When Fisheye is connected directly to multiple user directories, where duplicate user names and group names are used across those directories, the effective group memberships that Fisheye uses for authorization can be determined using either of these two schemes:
- 'aggregating membership'
- 'non-aggregating membership'.
See Effective memberships with multiple directories for more information about these two schemes.
注意:
- Aggregating membership is used by default for new installations of Fisheye.
- Authentication, for when Fisheye is connected to multiple directories, only depends on the mapped groups in those directories – the aggregation scheme is not involved at all.
- The directory order is significant during the authentication of the user, in cases where the same user exists in multiple directories. When a user attempts to log in, the application will search the directories in the order specified, and will use the credentials (password) of the first occurrence of the user to validate the login attempt.
- For inactive users, Fisheye only checks if the user is active in the first (highest priority) directory in which they are found for the purpose of determining authentication. Whether a user is active or inactive does not affect how their memberships are determined.
- ユーザーがグループに追加されると、ユーザーは利用可能な最初の書き込み可能なディレクトリ (優先度順) にのみ追加されます。
- ユーザーがグループから削除されると、non-aggregating が使用されている場合、ユーザーは検出された最初のディレクトリのグループからのみ削除されます。aggregating membership が使用されている場合、ユーザーが存在するすべてのディレクトリのグループから削除されます。
- When using Single Sign-On with Crowd and multiple Crowd directories:
- signed-in users will be validated against the first Crowd directory the user is in
- users that haven't signed in yet, but have a valid Crowd SSO cookie will be validated against all configured Crowd directories in order
A Fisheye admin can change the membership scheme used by Fisheye using the following commands:
aggregating membership に変更するには、次のコマンドで、
<username>
、<password>
、および<base-url>
を自身の値で置き換えます。curl -H 'Content-type: application/json' -X PUT -d '{"membershipAggregationEnabled":true}' -u <username>:<password> <base-url>/rest/crowd/latest/application
aggregating membership に変更するには、次のコマンドで
<username>
、<password>
、および<base-url>
を自身の値で置き換えます。curl -H 'Content-type: application/json' -X PUT -d '{"membershipAggregationEnabled":false}' -u <username>:<password> <base-url>/rest/crowd/latest/application
Note that these operations are different from how you make these changes in Crowd. Note also that changing the aggregation scheme can affect the authorization permissions for your users, and how directory update operations are performed.