On 04/21/15 11:43, Ulrich Windl wrote:

...

...

...

dE de.techno@gmail.com schrieb am 20.04.2015 um 07:36 in Nachricht

55349047.7020907@gmail.com:

...

On 04/20/15 00:59, Ryan Tandy wrote:

...

On Sun, Apr 19, 2015 at 11:42:16AM +0530, dE wrote:

...

As per https://tools.ietf.org/html/rfc4512#section-3.3

When creating an entry or adding an 'objectClass' value to an entry, all superclasses of the named classes SHALL be implicitly added as well if not already present.

That means the top object class will always be there.

Basically correct. Note "implicitly" means it's treated as present, even if the entry doesn't actually contain "objectClass: top".

...

Or is it that only the most subordinate object class in the multivalued attribute is considered by the client and server?

The following facts may answer your question:

• every entry satisfies the filter "(objectClass=top)".

• an entry with "objectClass: inetOrgPerson" satisfies the filter "(objectClass=person)".

I'm concerned about the attributes. Does adding of the top object class (or person) add all attributes to the entry?

I'd say: It adds no attributes at all to the entry automagically, but the MUST attributes have to be provided while the MAY attributes may be provided. If an entry is created, it will contain all the valid attributes you provide (no entry is created if you supply invalid attributes).

Regards, Ulrich

Yes, so subclasses do not define MAY; it's defined by the MAY of the top object class.