Details
-
Bug
-
Resolution: Timed out
-
Medium
-
None
-
2.0.2
-
Severity 2 - Major
-
Description
Hello everyone,
We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Timed Out.
Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Crowd team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.
We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.
Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.
Thank you,
Crowd Team
Greetings,
I've noticed this issue in the past, but didn't know what was causing it until I sat down to figure it out today.
When an entry is created in an OpenLDAP-backed directory, it is generally given a schema with only the objectClass of inetOrgPerson. This works sufficiently in a standalone configuration, but as soon as the directory is used more exhaustively, problems arise.
Here is the Apache DS console output created while adding the posixAccount objectClass and it's MUST attributes to an entity created by Crowd:
#!RESULT ERROR #!CONNECTION ldap://dev.itdatabase.com:389 #!DATE 2009-11-27T16:15:37.605 #!ERROR [LDAP: error code 20 - modify/add: objectClass: value #0 already exists] dn: cn=brian,ou=people,dc=itdatabase,dc=com changetype: modify add: uid uid: topping - add: gidNumber gidNumber: 500 - add: objectClass objectClass: top objectClass: posixAccount - add: homeDirectory homeDirectory: /home/topping -
This leads to #!ERROR LDAP: error code 20 - modify/add: objectClass: value #0 already exists
With some experimentation, it's clear that this failure does not occur if the entity is created with all the inheritors of inetOrgPerson. This is true for both JXplorer and Apache DS Studio, so it is not like this is a problem isolated to a single browser.
Would it be possible for Crowd to start creating entities with the top, person and organizationalPerson objectClasses as well?
