Users Removed When Synchronizing With JIRA/Crowd
Fisheye/Crucible is connected to JIRA/Crowd for user authentication and users are created automatically when logging in if "Auto-add" is enabled. However, when synchronising, the JIRA/Crowd users are removed and the following can be seen in the logs:
2013-03-19 13:39:14,148 INFO [quartzScheduler_Worker-9 ] fisheye UserSynchroniserJob-execute - Starting resynchronising users 2013-03-19 13:39:14,304 INFO [quartzScheduler_Worker-9 ] fisheye DefaultUserManager-synchroniseUsers - resynchronising users with crowd 2013-03-19 13:39:15,085 INFO [quartzScheduler_Worker-9 ] fisheye DefaultUserManager$24-doInTransaction - 'admin' has been deactivated in FishEye. 2013-03-19 13:39:15,335 INFO [quartzScheduler_Worker-9 ] fisheye DefaultUserManager$24-doInTransaction - 'user1' has been deactivated in FishEye. 2013-03-19 13:39:15,710 INFO [quartzScheduler_Worker-9 ] fisheye DefaultUserManager$24-doInTransaction - 'user2' has been deactivated in FishEye.
The following REST API call (for Crowd only) checks if the user belongs to the groups set in the configuration:
Logging in with the "Application Name" and "Password" set in the configuration for REST API will be required.
The JIRA/Crowd users are not members of the groups configured to be synchronised.
There are two possible resolutions:
- Add the missing groups to be synchronised with Fisheye/Crucible under
Administration > Security Settings > Authentication > JIRA/Crowd Authentication.
- Add the missing users to the groups already being synchronised.