-
Bug
-
Resolution: Low Engagement
-
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
-
-
- Closed
-
-
-
- Closed
-
[CONFSERVER-38736] JIRA 6.4 as a Crowd Server does not work with Confluence version 5.7.x and above
This is exactly the same problem as Stash experienced with JIRA 6.4. The workaround there of upgrading to JIRA 6.4.1 applies to this issue as well.
What do the JIRA logs say when this happens? The stack trace says to check there for details of why a GroupWithAttributes is not a String or a Group.
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
Please note the comments on this thread are not being monitored.
You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Confluence Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Confluence Data Center