I think the Admin guide is accurate -- it tells you exactly what format to use if you want to define auxiliary object classes. Whether and how to use them is a different matter & you should probably send such questions to a general list, not to the OpenLDAP list.
Regardless, you are misunderstanding this -- add the auxiliary objectclass to the entry as usual.
For example, if you define an auxiliary objectclass called QurisMixin, here is an LDIF entry that belongs to that objectclass:
From: Alan Sparks [mailto:firstname.lastname@example.org]
Sent: Wednesday, February 13, 2002 1:21 PM
Subject: Defining/using auxiliary objectclass - how?
Some tutalage please. Trying to grok this without great success.
OpenLDAP admin guide, section 188.8.131.52 discusses auxiliary object
classes, and states:
"To define an auxiliary object class which allows myPhoto to be added to
any existing entry."
My initial reading of this was that such a class would "mix in" without
requiring the auxiliary objectclass to be explicitly added to each
object. This doesn't seem to work... I get attribute violations loading
stuff, until I explicitly name the aux class in the LDIF object.
Am I misunderstanding this?
For reference, using the latest 2.0.23 OpenLDAP release, with something
that looks like:
objectclass ( 184.108.40.206.4.1.113220.127.116.11 NAME 'QurisMixin'
DESC 'mix in Quris enterprise attributes'
SUP top AUXILIARY
MAY ( accountdisabled $ yahoomessengerid ) )
(originally tried it without the "SUP top", with same unhelpful result.)
Thanks in advance.
Alan Sparks, Sr. UNIX Administrator email@example.com
Quris, Inc. (720) 836-2058