On 04/21/15 11:43, Ulrich Windl wrote:
dE de.techno@gmail.com schrieb am 20.04.2015 um 07:36 in Nachricht
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.
--On Tuesday, April 28, 2015 10:58 AM +0530 dE de.techno@gmail.com wrote:
Yes, so subclasses do not define MAY; it's defined by the MAY of the top object class.
The "top" objectClass does not contain *any* MAY attributes. I wonder if you are confused in thinking of "top" as a generic term. It is not. "top" is a very specific objectClass that is explicitly defined as noted previously. It contains a single MUST attribute.
--Quanah
--
Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration
Hi,
On Mon, 27 Apr 2015, Quanah Gibson-Mount wrote:
--On Tuesday, April 28, 2015 10:58 AM +0530 dE de.techno@gmail.com wrote:
Yes, so subclasses do not define MAY; it's defined by the MAY of the top object class.
The "top" objectClass does not contain *any* MAY attributes. I wonder if you are confused in thinking of "top" as a generic term. It is not. "top" is a very specific objectClass that is explicitly defined as noted previously. It contains a single MUST attribute.
one of my customers has an enterprise provisioning tool from a well known large supplier of such systems.
The developers of that tool insist that they want to see an explit "objectClass: top" in all objects.
It hurts every single time I have to look at that specific directory.
Greetings Christian
On 04/28/15 13:22, Christian Kratzer wrote:
Hi,
On Mon, 27 Apr 2015, Quanah Gibson-Mount wrote:
--On Tuesday, April 28, 2015 10:58 AM +0530 dE de.techno@gmail.com wrote:
Yes, so subclasses do not define MAY; it's defined by the MAY of the top object class.
The "top" objectClass does not contain *any* MAY attributes. I wonder if you are confused in thinking of "top" as a generic term. It is not. "top" is a very specific objectClass that is explicitly defined as noted previously. It contains a single MUST attribute.
one of my customers has an enterprise provisioning tool from a well known large supplier of such systems.
The developers of that tool insist that they want to see an explit "objectClass: top" in all objects.
It hurts every single time I have to look at that specific directory.
Greetings Christian
Thank you everyone for the help!
I under now.
openldap-technical@openldap.org
-
Christian Kratzer -
dE -
Quanah Gibson-Mount