[Date Prev][Date Next]
Re: Quick Start Guide
On Sat, 7 Aug 1999, Kurt D. Zeilenga wrote:
Simon Murcott wrote:
> Under the "Add initials items..." section you have an object with two
> "objectClass"es in it. When using multiple "objectClass" attributes one should
> first add "objectClass: top".
Actually, I disagree. When adding an entry you should specify one structural
object class and any number of auxilary object classes. You should avoid
listing abstract object classes such as top. The server will do The Right Thing (tm).
With LDAPv2 (such as OpenLDAP 1.x), the server can just accept the input after
doing it's schema checks. Servers may or may not add unlisted superior object
classes to the entry. (OpenLDAP 1.2 implements "not").
With LDAPv3, the server is required to add all unlisted superior object classes
of the named object classes upon add/modify of the entry. This behavior is
specified in RFC 2251, 3.2.1. This behavior is being implemented in -devel
for release with OpenLDAP 2.0.
So are you trying to say that under LDAPv2 one does not need "objectClass: top"
but under LDAPv3 one does?
Optimation New Zealand Limited
Exchange Place, Willeston Street, Wellington, New Zealand
Phone +64 4 4727218, Fax +64 4 4727219, Mobile 025 405821
A closed mouth gathers no foot.