-
Bug
-
Resolution: Fixed
-
Medium
-
0.4.5
-
None
-
None
-
Openldap 2.3.30
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.
- was cloned as
-
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
-
- Closed
-
[CWD-180] Schema violation with LDAP and Groups/Roles
Workflow | Original: Simplified Crowd Development Workflow v2 - restricted [ 1509375 ] | New: JAC Bug Workflow v3 [ 3364540 ] |
Workflow | Original: Simplified Crowd Development Workflow v2 [ 1391258 ] | New: Simplified Crowd Development Workflow v2 - restricted [ 1509375 ] |
Workflow | Original: Crowd Development Workflow v2 [ 272258 ] | New: Simplified Crowd Development Workflow v2 [ 1391258 ] |
Workflow | Original: JIRA Bug Workflow v2 [ 173520 ] | New: Crowd Development Workflow v2 [ 272258 ] |
Workflow | Original: jira [ 77634 ] | New: JIRA Bug Workflow v2 [ 173520 ] |
Component/s | Original: Connector [ 11554 ] |
Assignee | Original: Justen Stepka [Atlassian] [ justen.stepka@atlassian.com ] | |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Switched the group add to take care of adding an empty membership. Also noticed that the default filters for OpenLDAP are not correct.