[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Auxiliary object class practically of no use?

dE wrote:

According to RFC 4512

An entry can belong to any subset of the set of auxiliary object
    classes allowed by the DIT content rule associated with the
    structural object class of the entry.

 From what I understand, this means auxiliary classes do not 'augment'; the
no. of attributes which are possible in an entry must be a subset of the
structural object class the entry belongs to.


You're mixing two things here:
- Auxiliary object classes
- DIT content rules
Basically auxiliary object classes do augment the set of attributes usable in an entry. That's what they are for. 

DIT content rules can limit the set of auxiliary object classes with AUX.
You might want to have a look at the diagram (slide 14) herein which shows the relations between the various subschema descriptions: 

http://www.stroeder.com/publications.shtml#ldapcon2013

Bug: Unfortunately the SUP loop link for attribute types is missing...

Ciao, Michael.

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature