Authentication Plugins do not use the Atlassian Plugins framework - they are simply a jar
added to Fisheye's classpath.
To implement an arbitrary form of authentication and authorisation for Fisheye you need to provide a class which extends com.cenqua.fisheye.user.plugin.AbstractFishEyeAuthenticator. You can find more information about custom Fisheye authorisation in the online javadocs and the library jar.
For Fisheye to use the authenticator, it must be compiled, placed in a jar archive and then put in the $FISHEYE_INST/lib
directory. If other third-party libraries are required by your authenticator, they must also be in the $FISHEYE_INST/lib
directory.
After implementing a custom authenticator, the next step is to configure Fisheye to use it.
Click Setup Custom authentication on the Fisheye Admin > Users/Security page.
You will be presented with a form containing the following fields to be set:
Classname | The fully qualified class name of your AbstractFishEyeAuthenticator, e.g. |
Cache TTL (positive) | How long Fisheye should cache permission checks. Example values are: |
Auto-add | Fisheye can automatically create a user it has not previously encountered if the user can successfully authenticate against your authenticator. |
Properties | Any properties your authenticator requires. These will be passed to its
|
You may also require a per-repository constraint to restrict access to specific repositories using your custom authenticator. If a custom authenticator is set, then the Permissions summary table will display the constraint per repository and a link to enable you to edit it.
The Authentication Test page allows you to enter a user's credentials and to test the user's authentication. It will also test which repositories the user is authorised to access.
Rate this page: