RE: [Heimdal PATCH] LDAP backend support for OpenLDAP 2.1.x

["Howard Chu" <hyc@highlandsun.com>]

> -----Original Message-----
> From: Luke Howard [mailto:lukeh@PADL.COM]

> >-	ret = LDAP_addmod(&mods, LDAP_MOD_ADD, "objectClass", "person");
> >+	/* person is the old structural object class */
> >+	/* From the OpenLDAP FAQ-O-Matic: A common error that
> is encountered when    */
> >+	/* upgrading from earlier versions of OpenLDAP is
> 'invalid structural object */
> >+	/* class chain'. This occurs because 2.1.x versions
> enforce more of the LDAP */
> >+	/* structure rules than 2.0.x did, and many directories
> contain incorrect    */
> >+	/* data because of the lax checking of the earlier
> versions.                 */
> >+
> >+	/* So we could avoid this problem using the
> OpenLDAPperson objectclass       */
> >+	/* instead of the person object class */
> >+	ret = LDAP_addmod(&mods, LDAP_MOD_ADD, "objectClass",
> "OpenLDAPperson" );
> > 	if (ret != 0) {
> > 	    goto out;
>
> What's the rationale behind this?

I don't quite understand this one either. I'm guessing the change in
objectclass is just to get an object that allows the 'uid' attributeType.
Jose, is that the idea?

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support