Synchronising With Large User Repositories

When FishEye synchronises with external user repositories (LDAP, AD or Crowd) it adds all visible users in the repository, even if you do not want all these users to have access to FishEye.

For example you may have restricted viewing permissions to your repositories to a single LDAP group (using a filter). However the synchronise button will import all your LDAP users, because each of these users will be able to log into fisheye, even though they will not have permission to view any repository.

This is unavoidable, as users may create another repository in the future or a repository with no group based restrictions.

Also if you have a large number of users in you LDAP, then a synchronise needs to check if for each user within Fisheye, to see if they still exist in LDAP and for each user in LDAP to see if they exist in Fisheye. This can be quite taxing when you have a large user base. It will also require more memory and could lead to

OutOfMemoryError: Java Heap Space errors.

Additionally, when setting up external authentication for large repositories: set "Synchronise users with LDAP" to no. Next turn on "Auto-add" users to on, so that any External user that matches your defined user filter who logs into FishEye, will be added as a user (NOTE: Auto-add does not mean any user will have access to FishEye, only users that can successful authenticate against your LDAP server, using the settings you have defined within FishEye, will be added. They first must pass the authentication before they will be added).

You should always try to restrict your user filter when setting up your LDAP authentication to only match the small subset of users that should have access to Fisheye.