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

Crowd adds a blank user when creating a new group, which it does not overwrite when adding the first user to the group

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Medium Medium
    • None
    • 2.0
    • Directory - LDAP
    • None

    • Openldap 2.3.30

      After CWD-180 is fixed, it seems Crowd+OpenLDAP will create groups with a blank uniqueMember (position 1) in it to satisfy the schema. However, subsequently, if you add an user to the group, it will create another uniqueMember instead of writing to the first blank one. So the end result is for a group with only one valid user, there will be two counts of uniqueMember in it.

      This is causing problem on scripts that's expecting a value on the first uniqueMember, and affecting the total count as well. All in all, Crowd doesn't seem to have enough checks to ensure the integrity of the LDAP database, e.g. CWD-1184.

      Thanks,

          Form Name

            [CWD-1213] Crowd adds a blank user when creating a new group, which it does not overwrite when adding the first user to the group

            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Simplified Crowd Development Workflow v2 - restricted [ 1511024 ] New: JAC Bug Workflow v3 [ 3365962 ]
            Mareusz (Inactive) made changes -
            Resolution New: Obsolete [ 11 ]
            Status Original: Open [ 1 ] New: Closed [ 6 ]
            Bugfix Automation Bot made changes -
            Support reference count New: 2
            Owen made changes -
            Symptom Severity Original: Major [ 14431 ] New: Severity 2 - Major [ 15831 ]
            jonah (Inactive) made changes -
            Symptom Severity New: Major [ 14431 ]
            Owen made changes -
            Workflow Original: Simplified Crowd Development Workflow v2 [ 1392943 ] New: Simplified Crowd Development Workflow v2 - restricted [ 1511024 ]
            Owen made changes -
            Workflow Original: Crowd Development Workflow v2 [ 273437 ] New: Simplified Crowd Development Workflow v2 [ 1392943 ]
            jawong.adm made changes -
            Workflow Original: JIRA Bug Workflow v2 [ 174464 ] New: Crowd Development Workflow v2 [ 273437 ]
            Status Original: Reopened [ 4 ] New: Open [ 1 ]
            David O'Flynn [Atlassian] made changes -
            Fix Version/s Original: 1.0 [ 12672 ]
            Affects Version/s New: 2.0 [ 12269 ]
            Affects Version/s Original: 0.4.5 [ 12652 ]
            Description Original: Trying to add groups (or roles) on a clean openldap directory I obtain the following error:

            18:00:42,095 ERROR crowd.console.action.group.AddGroup: Operation failed; nested exception is javax.naming.directory.SchemaViolationException: [LDAP: error code 65 - object class 'groupOfUniqueNames' requires attribute 'uniqueMember']; remaining name 'cn=Test,ou=Groups,dc=XXXX,dc=XXX'

            It seems Crowd tries to add the group entry without using the attribute uniquemember.

            Same thing happens for Roles, while the creation of principals works fine.

            		New: After CWD-180 is fixed, it seems Crowd+OpenLDAP will create groups with a blank uniqueMember (position 1) in it to satisfy the schema. However, subsequently, if you add an user to the group, it will create another uniqueMember instead of writing to the first blank one. So the end result is for a group with only one valid user, there will be two counts of uniqueMember in it.

            This is causing problem on scripts that's expecting a value on the first uniqueMember, and affecting the total count as well. All in all, Crowd doesn't seem to have enough checks to ensure the integrity of the LDAP database, e.g. CWD-1184.

            Thanks,
            Summary Original: CLONE -Schema violation with LDAP and Groups/Roles New: Crowd adds a blank user when creating a new group, which it does not overwrite when adding the first user to the group
            David O'Flynn [Atlassian] made changes -
            Resolution Original: Obsolete [ 11 ]
            Status Original: Resolved [ 5 ] New: Reopened [ 4 ]

              Unassigned Unassigned
              e4e8cbc506a4 Alvin Chang
              Affected customers:
              0 This affects my team
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: