Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-25611

Unable to modify group memberships for re-created users

      NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

      Using standalone Crowd as an external directory (internal directory disabled):

      • create a user (the 'original' user),
      • add the user to some groups,
      • delete the user,
      • create a new user with same username,
      • remove them from all groups,
      • restart JIRA.

      After JIRA restarts, the user will be in all the groups the original user was in, and it will be impossible to remove them from any of these groups.

            [JRASERVER-25611] Unable to modify group memberships for re-created users

            Renata Dornelas made changes -
            Remote Link Original: This issue links to "Page (Atlassian Documentation)" [ 65322 ]

            @Michael Knight: What is the risk involved in running the cleanup query without shutting down JIRA?

            Nagarajan Gopalan added a comment - @Michael Knight: What is the risk involved in running the cleanup query without shutting down JIRA?
            Bugfix Automation Bot made changes -
            Minimum Version New: 4.03

            Uwe Schindler added a comment - - edited

            In my JIRA database I had similar problem (because the fix in this issue only prevented the creation of the junk). Interestingly, we migrated the database from mysql to postgresql through JIRA's backup/restore, but the junk entries survived this.

            I was able to delete the junk entries (before that I checked with a select, what I would delete – and it actually showed the broken users). After executing the delete statement and restarting JIRA, all was fixed. Check for incorrect entries:

            select * from cwd_membership where child_id not in (select id from cwd_user);
            

            This should show the affected users and groups together with other information.

            Nevertheless, wouldn't it be a good idea to add the above check to the database integrity check available from the JIRA admin GUI?

            Uwe Schindler added a comment - - edited In my JIRA database I had similar problem (because the fix in this issue only prevented the creation of the junk). Interestingly, we migrated the database from mysql to postgresql through JIRA's backup/restore, but the junk entries survived this. I was able to delete the junk entries (before that I checked with a select, what I would delete – and it actually showed the broken users). After executing the delete statement and restarting JIRA, all was fixed. Check for incorrect entries: select * from cwd_membership where child_id not in ( select id from cwd_user); This should show the affected users and groups together with other information. Nevertheless, wouldn't it be a good idea to add the above check to the database integrity check available from the JIRA admin GUI?
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2828434 ] New: JAC Bug Workflow v3 [ 2920774 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2548631 ] New: JAC Bug Workflow v2 [ 2828434 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1542294 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2548631 ]
            jonah (Inactive) made changes -
            Description Original: Using standalone Crowd as an external directory (internal directory disabled):
            * create a user (the 'original' user),
            * add the user to some groups,
            * delete the user,
            * create a new user with same username,
            * remove them from all groups,
            * restart JIRA.

            After JIRA restarts, the user will be in all the groups the original user was in, and it will be impossible to remove them from any of these groups.
            New: {panel:bgColor=#e7f4fa}
              *NOTE:* This bug report is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JRACLOUD-25611].
              {panel}

            Using standalone Crowd as an external directory (internal directory disabled):
            * create a user (the 'original' user),
            * add the user to some groups,
            * delete the user,
            * create a new user with same username,
            * remove them from all groups,
            * restart JIRA.

            After JIRA restarts, the user will be in all the groups the original user was in, and it will be impossible to remove them from any of these groups.
            jonah (Inactive) made changes -
            Link New: This issue relates to JRACLOUD-25611 [ JRACLOUD-25611 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: affects-server ondemand todo New: affects-cloud affects-server ondemand todo

              andreask@atlassian.com Andreas Knecht (Inactive)
              mknight@atlassian.com Michael Knight
              Affected customers:
              1 This affects my team
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: