-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
5.7.5, 5.8.4, 5.8.8
-
6
-
Severity 2 - Major
-
Summary
There is a known compatibility issue that prevents the user management synchronisation between JIRA 6.4 and Confluence 5.7.x and above.
This will only affect you if you use JIRA to manage your Confluence users. The bug in JIRA is being tracked on JRA-42566.
Environment
- Confluence version: 5.7.x, 5.8.x
- JIRA version: 6.4
Steps to Reproduce
- Case 1
- Set up Confluence 5.7.x and above with JIRA 6.4 configured as its User Management Server. To perform that, please refer to Connecting Confluence to JIRA for user management.
- Perform Synchronisation.
- Case 2
- Install Confluence 5.7.x and above as per the Confluence Setup Guide documentation.
Instead of managing users and groups within Confluence itself, choose Connect to JIRA and setup JIRA External User Management (JIRA 6.4 instance) instead.
- Install Confluence 5.7.x and above as per the Confluence Setup Guide documentation.
Expected Results
Synchronisation should work successfully as per expected.
Actual Results
Synchronisation fails and the below exception is thrown in the atlassian-confluence.log file:
2015-07-22 13:49:12,755 INFO [Long running task: Synchronising JIRA Directory] [atlassian.crowd.directory.DbCachingRemoteDirectory] synchroniseCache failed synchronisation complete for directory [ 131073 ] in [ 946ms ] 2015-07-22 13:49:12,768 ERROR [Long running task: Synchronising JIRA Directory] [confluence.setup.actions.ConnectToJiraSyncDirectoryAction$SyncJiraDirectory LongRunningTask] runInternal Synchronization failed. -- referer: http://localhost:8090/setup/connecttojira-start.action | url: /setup/connecttojirasyncdirectory-start.action | userName: anonymous | action: co nnecttojirasyncdirectory-start com.atlassian.crowd.exception.runtime.OperationFailedException: Error from Crowd server propagated to here via REST API (check the Crowd server logs for det ails): Class type for return values ('interface com.atlassian.crowd.model.group.GroupWithAttributes') is not 'String' or 'Group' at com.atlassian.crowd.embedded.core.CrowdDirectoryServiceImpl.synchroniseDirectory(CrowdDirectoryServiceImpl.java:208) at com.atlassian.confluence.setup.actions.ConnectToJiraSyncDirectoryAction$SyncJiraDirectoryLongRunningTask.runInternal(ConnectToJiraSyncDirectoryAc tion.java:213) ... Caused by: com.atlassian.crowd.integration.rest.service.CrowdRestException: Class type for return values ('interface com.atlassian.crowd.model.group.GroupWithAttributes') is not 'String' or 'Group' at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.throwError(RestExecutor.java:656) at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.andReceive(RestExecutor.java:485) at com.atlassian.crowd.integration.rest.service.RestCrowdClient.searchGroupsWithAttributes(RestCrowdClient.java:572)
Workaround
This is a bug in JIRA 6.4 and is fixed in JIRA 6.4.1. The preferred solution is to upgrade to JIRA 6.4.1.
- is related to
-
BSERV-7195 JIRA 6.4 as a Crowd Server does not work with Stash 3.4.3 or higher
- Closed
-
JRASERVER-42566 JIRA 6.4 as a Crowd Server does not work with Stash 3.4.3 or higher
- Closed