Hi, LDAP allows a single branch of structural objectClasses hierarchy to be added to an entry. So top, person, inetOrgPerson are possible objectClass values for an entry, but you cannot add an organizationalUnit in that group.
If ApacheDS allows you to do something different, than just file a Jira issue. On 5/10/07, Martin Marcher <[EMAIL PROTECTED]> wrote:
hello, I'm putting our autofs in ldap now and wanted to be extra smart and added dn: ou=auto.master,dc=example,dc=com objectClass: automountMap objectClass: organizationalUnit objectClass: top ou: auto.master now ldapstudio shows me that both automountMat and organizationalUnit are structural. I read somewhere (http://www.oav.net/mirrors/ldapv3.pdf page 22f not exactly a reference but that was the first place i found it again) that this is a violation for LDAP as there is only one structural objectClass allowed and others should be auxiliary. Do I have wrong infos here or did I find something? cheers martin -- Martin Marcher [EMAIL PROTECTED] http://www.mycorners.com https://www.xing.com/profile/Martin_Marcher http://www.linkedin.com/in/martinmarcher http://www.studivz.net/profile.php?ids=9f83ea8c5996b8ec http://www.amazon.de/gp/registry/wishlist/3KDAGCL2NKOIM/ref=reg_hu-wl_goto-registry/302-4432803-5146435?ie=UTF8&sort=date-added
-- Ersin
