Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-4019

Group membership leak after user recreation

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Medium Medium
    • None
    • 2.7.1
    • User Management
    • None

    • Standalone, Ubuntu 14.04

      Java:
      java version "1.7.0_55"
      OpenJDK Runtime Environment (IcedTea 2.4.7) (7u55-2.4.7-1ubuntu1)
      OpenJDK 64-Bit Server VM (build 24.51-b03, mixed mode)

      Setup:
      1) Using crowd (v2.7.1) as external directory (read-write) for jira (v6.1.4).
      2) Using the SingleSignOn Connector from seraph-config.xml
      3) crowd is connected to OpenLDAP (also r/w)

      Steps to reproduce:
      1) Delete a user, which has active group memberships, in jira
      2) Create a user with the same name in jira

      Problem:
      1) The "User delete" seems to be correctly synchronized with crowd (at least the user is no longer displayed, haven't looked at the database so far)
      2) After the recreation, the former group memberships are "restored" (in crowd and in jira)

      May somehow be related to https://jira.atlassian.com/browse/JRA-25611 , however it seems not to be fixed so far.

      Kind regards,

      Sebastian Lotter

            [CWD-4019] Group membership leak after user recreation

            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Simplified Crowd Development Workflow v2 - restricted [ 1509770 ] New: JAC Bug Workflow v3 [ 3364747 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Simplified Crowd Development Workflow v2 [ 1392121 ] New: Simplified Crowd Development Workflow v2 - restricted [ 1509770 ]
            Owen made changes -
            Workflow Original: Crowd Development Workflow v2 [ 723284 ] New: Simplified Crowd Development Workflow v2 [ 1392121 ]

            Sebastian Lotter added a comment -

            @Joseph: Thanks for the fast response.

            Sebastian Lotter added a comment - @Joseph: Thanks for the fast response.
            joe made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]
            joe made changes -
            Link New: This issue duplicates CWD-3138 [ CWD-3138 ]

            joe added a comment -

            This is due to memberships not being deleted from LDAP when the user is deleted; I've linked to another report for this case.

            joe added a comment - This is due to memberships not being deleted from LDAP when the user is deleted; I've linked to another report for this case.
            Sebastian Lotter created issue -

              Unassigned Unassigned
              25dd1788631f Sebastian Lotter
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: