Re: LDAPSubentry

["Kurt D. Zeilenga" <Kurt@OpenLDAP.org>]

The 'ldapSubentry' class was defined for operational purposes,
not user application purposes.  Hence, your use of it is/was
inappropriate.  Likewise, 'subentry' is defined for operational
purposes.  2.1, unlike 2.0, protects against misuse of object
classes defined purposes.

You should use an object class intended for your purpose.

At 01:23 AM 5/21/2003, Luke Dudney wrote:
>I've been using OpenLDAP 2.0.x for a while and now wish to upgrade to 2.1. I was using the LDAPsubEntry objectClass to provide subentries in the directory but this objectclass has disappeared in 2.1 I've done a slapcat from 2.0, changed instances of 'LDAPsubEntry' to 'subentry' but I get "(65) objectClass "2.5.17.0" not supported in context"
>
>Below is an example of how I was using LDAPSubEntry. Does anyone have any example of how to achieve the same thing in 2.1 ?
>
>tia
>Luke
>
>
># Whitelist, WAGOV, AU
>dn: cn=Whitelist,o=WAGOV,c=AU
>objectClass: top
>objectClass: LDAPsubEntry
>cn: Whitelist
>
># Domains, Whitelist, WAGOV, AU
>dn: cn=Domains,cn=Whitelist,o=WAGOV,c=AU
>objectClass: top
>objectClass: labeledURIObject
>objectClass: LDAPsubEntry
>cn: Domains
>cn: Whitelist
>labeledURI: gov.au
>labeledURI: whitepages.com.au
>labeledURI: australiapost.com.au
>labeledURI: yellowpages.com.au
>labeledURI: edu.au
>
># URLs, Whitelist, WAGOV, AU
>dn: cn=URLs,cn=Whitelist,o=WAGOV,c=AU
>objectClass: top
>objectClass: labeledURIObject
>objectClass: LDAPsubEntry
>cn: URLs
>cn: Whitelist
>