Configuring external authentication sources

Although FishEye always maintains a list of users internally, you can have FishEye authenticate and authorise users against one or more external authentication sources.

Be aware that you can force usernames to become lowercase on import.

When a user is renamed in an external authentication service they must also be renamed in FishEye/Crucible.

Single External Authentication Source

To set an external authentication source, click Authentication in the Admin menu. You can only set up one external authentication source and each repository has the choice of authenticating against that or the internal repository. To change the external authentication source, you will need to remove the settings that are already configured, by clicking Remove. You will then see the option to add a different authentication source.

FishEye currently supports:

• LDAP authentication
• Host-Based Authentication – Using PAM on Linux/Solaris/OS-X and Local/Domain Accounts on Windows
• Using AJP with FishEye
• Custom authentication
• JIRA Authentication – Using Atlassian's JIRA to manage your users and groups. Note that you can't use JIRA Cloud to manage your FishEye or Crucible users.  

Multiple External Authentication Sources

The recommended approach to authenticating against more than one authentication source is to implement single signon (SSO). You can integrate FishEye with an existing SSO solution, or add Atlassian Crowd integration to combine users and authentication from multiple external user repositories. Crowd connectors are already available for all Atlassian products, LDAP, Active Directory and Subversion:

• Crowd Authentication
• Custom authentication