com.atlassian.crowd.exception.runtime.OperationFailedException: Group already exists

Atlassian JIRA | James Wong | 6 years ago
  1. 0

    Attempting to add a user to a group before the groups have been sync'ed from the remote directory results in the following stack trace: {noformat} com.atlassian.crowd.exception.runtime.OperationFailedException: Group already exists at com.atlassian.crowd.embedded.core.CrowdAdminServiceImpl.addUserToGroup(CrowdAdminServiceImpl.java:396) at com.atlassian.jira.user.util.UserUtilImpl.doAddUserToGroup(UserUtilImpl.java:501) at com.atlassian.jira.user.util.UserUtilImpl.addUserToGroup(UserUtilImpl.java:479) at com.atlassian.jira.user.util.UserUtilImpl.addUserToGroups(UserUtilImpl.java:516) at com.atlassian.jira.bc.group.DefaultGroupService.addUsersToGroups(DefaultGroupService.java:331) at com.atlassian.jira.web.action.admin.user.EditUserGroups.doExecute(EditUserGroups.java:85) at webwork.action.ActionSupport.execute(ActionSupport.java:165) at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:58) at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:139) at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.service(JiraWebworkActionDispatcher.java:168) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) {noformat} Steps to reproduce: * Create a read/write LDAP Directory in Jira. * Browse for a user that exists in LDAP (using the User Browser). * Select "Groups" link to edit groups * Select the "jira-users" from the list and click "Join" Expected: * User successfully added to "jira-users"

    Atlassian JIRA | 6 years ago | James Wong
    com.atlassian.crowd.exception.runtime.OperationFailedException: Group already exists
  2. 0

    Attempting to add a user to a group before the groups have been sync'ed from the remote directory results in the following stack trace: {noformat} com.atlassian.crowd.exception.runtime.OperationFailedException: Group already exists at com.atlassian.crowd.embedded.core.CrowdAdminServiceImpl.addUserToGroup(CrowdAdminServiceImpl.java:396) at com.atlassian.jira.user.util.UserUtilImpl.doAddUserToGroup(UserUtilImpl.java:501) at com.atlassian.jira.user.util.UserUtilImpl.addUserToGroup(UserUtilImpl.java:479) at com.atlassian.jira.user.util.UserUtilImpl.addUserToGroups(UserUtilImpl.java:516) at com.atlassian.jira.bc.group.DefaultGroupService.addUsersToGroups(DefaultGroupService.java:331) at com.atlassian.jira.web.action.admin.user.EditUserGroups.doExecute(EditUserGroups.java:85) at webwork.action.ActionSupport.execute(ActionSupport.java:165) at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:58) at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:139) at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.service(JiraWebworkActionDispatcher.java:168) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) {noformat} Steps to reproduce: * Create a read/write LDAP Directory in Jira. * Browse for a user that exists in LDAP (using the User Browser). * Select "Groups" link to edit groups * Select the "jira-users" from the list and click "Join" Expected: * User successfully added to "jira-users"

    Atlassian JIRA | 6 years ago | James Wong
    com.atlassian.crowd.exception.runtime.OperationFailedException: Group already exists
  3. 0

    h5. 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|https://jira.atlassian.com/browse/JRA-42566]. \\ h5. Environment - Confluence version: 5.7.x, 5.8.x - JIRA version: 6.4 \\ h5. 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|https://confluence.atlassian.com/display/DOC/Connecting+to+Crowd+or+JIRA+for+User+Management#ConnectingtoCrowdorJIRAforUserManagement-ConnectingConfluencetoJIRAforUserManagement]. -# Perform Synchronisation. - Case 2 -# Install Confluence 5.7.x and above as per the [Confluence Setup Guide|https://confluence.atlassian.com/display/DOC/Confluence+Setup+Guide] documentation. (i) Instead of managing users and groups within Confluence itself, choose _Connect to JIRA_ and setup [JIRA External User Management|https://confluence.atlassian.com/display/DOC/Confluence+Setup+Guide#ConfluenceSetupGuide-8.SetupusermanagementUserMan] (JIRA 6.4 instance) instead. \\ h5. Expected Results Synchronisation should work successfully as per expected. \\ h5. Actual Results Synchronisation fails and the below exception is thrown in the atlassian-confluence.log file: {noformat} 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) {noformat} \\ h5. 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.

    Atlassian JIRA | 1 year ago | Lauretha Rura [Atlassian]
    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'
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    h5. 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|https://jira.atlassian.com/browse/JRA-42566]. \\ h5. Environment - Confluence version: 5.7.x, 5.8.x - JIRA version: 6.4 \\ h5. 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|https://confluence.atlassian.com/display/DOC/Connecting+to+Crowd+or+JIRA+for+User+Management#ConnectingtoCrowdorJIRAforUserManagement-ConnectingConfluencetoJIRAforUserManagement]. -# Perform Synchronisation. - Case 2 -# Install Confluence 5.7.x and above as per the [Confluence Setup Guide|https://confluence.atlassian.com/display/DOC/Confluence+Setup+Guide] documentation. (i) Instead of managing users and groups within Confluence itself, choose _Connect to JIRA_ and setup [JIRA External User Management|https://confluence.atlassian.com/display/DOC/Confluence+Setup+Guide#ConfluenceSetupGuide-8.SetupusermanagementUserMan] (JIRA 6.4 instance) instead. \\ h5. Expected Results Synchronisation should work successfully as per expected. \\ h5. Actual Results Synchronisation fails and the below exception is thrown in the atlassian-confluence.log file: {noformat} 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) {noformat} \\ h5. 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.

    Atlassian JIRA | 1 year ago | Lauretha Rura [Atlassian]
    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'
  6. 0

    Note: this issue may be related to [http://jira.atlassian.com/browse/CONFDEV-2776] but I open a separate issue since the stack is different. - In Jira: Add an LDAP directory and set it as Read-Only - In Jira: Add Confluence as an application. - In Confluence: Add Jira as a crowd server to the list of user directories, set is as Read/Write - In Confluence: Try to add a User *Expected*: Error message to propagate to UI *Actual*: Unhandled exception {code} com.atlassian.crowd.exception.runtime.OperationFailedException: com.atlassian.crowd.exception.ApplicationPermissionException: <?xml version="1.0" encoding="UTF-8" standalone="yes"?><error><reason>APPLICATION_PERMISSION_DENIED</reason><message>Cannot update user 'boss1' because directory 'ApacheDS 1' does not allow updates.</message></error> at com.atlassian.crowd.embedded.core.CrowdServiceImpl.updateUser(CrowdServiceImpl.java:343) caused by: com.atlassian.crowd.exception.ApplicationPermissionException: <?xml version="1.0" encoding="UTF-8" standalone="yes"?><error><reason>APPLICATION_PERMISSION_DENIED</reason><message>Cannot update user 'boss1' because directory 'ApacheDS 1' does not allow updates.</message></error> at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.throwError(RestExecutor.java:414) {code} - In Confluence: Try add a user from LDAP to a group. *Expected*: Error message to propagate to UI *Actual*: {code} com.atlassian.crowd.exception.runtime.OperationFailedException: com.atlassian.crowd.exception.ApplicationPermissionException: <?xml version="1.0" encoding="UTF-8" standalone="yes"?><error><reason>APPLICATION_PERMISSION_DENIED</reason><message>Cannot update group 'jira-developers' because directory 'ApacheDS 1' does not allow updates.</message></error> at com.atlassian.crowd.embedded.core.CrowdServiceImpl.addUserToGroup(CrowdServiceImpl.java:708) caused by: com.atlassian.crowd.exception.ApplicationPermissionException: <?xml version="1.0" encoding="UTF-8" standalone="yes"?><error><reason>APPLICATION_PERMISSION_DENIED</reason><message>Cannot update group 'jira-developers' because directory 'ApacheDS 1' does not allow updates.</message></error> at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.throwError(RestExecutor.java:414) {code}

    Atlassian JIRA | 6 years ago | Federico Silva Armas [Atlassian]
    com.atlassian.crowd.exception.runtime.OperationFailedException: com.atlassian.crowd.exception.ApplicationPermissionException: <?xml version="1.0" encoding="UTF-8" standalone="yes"?><error><reason>APPLICATION_PERMISSION_DENIED</reason><message>Cannot update group 'jira-developers' because directory 'ApacheDS 1' does not allow updates.</message></error>

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. com.atlassian.crowd.exception.runtime.OperationFailedException

      Group already exists

      at com.atlassian.crowd.embedded.core.CrowdAdminServiceImpl.addUserToGroup()
    2. com.atlassian.crowd
      CrowdAdminServiceImpl.addUserToGroup
      1. com.atlassian.crowd.embedded.core.CrowdAdminServiceImpl.addUserToGroup(CrowdAdminServiceImpl.java:396)
      1 frame
    3. com.atlassian.jira
      EditUserGroups.doExecute
      1. com.atlassian.jira.user.util.UserUtilImpl.doAddUserToGroup(UserUtilImpl.java:501)
      2. com.atlassian.jira.user.util.UserUtilImpl.addUserToGroup(UserUtilImpl.java:479)
      3. com.atlassian.jira.user.util.UserUtilImpl.addUserToGroups(UserUtilImpl.java:516)
      4. com.atlassian.jira.bc.group.DefaultGroupService.addUsersToGroups(DefaultGroupService.java:331)
      5. com.atlassian.jira.web.action.admin.user.EditUserGroups.doExecute(EditUserGroups.java:85)
      5 frames
    4. webwork.action
      ActionSupport.execute
      1. webwork.action.ActionSupport.execute(ActionSupport.java:165)
      1 frame
    5. com.atlassian.jira
      JiraActionSupport.execute
      1. com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:58)
      1 frame
    6. webwork.dispatcher
      GenericDispatcher.executeAction
      1. webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:139)
      1 frame
    7. com.atlassian.jira
      JiraWebworkActionDispatcher.service
      1. com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.service(JiraWebworkActionDispatcher.java:168)
      1 frame
    8. JavaServlet
      HttpServlet.service
      1. javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
      1 frame
    9. Glassfish Core
      ApplicationFilterChain.internalDoFilter
      1. org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
      1 frame