Subject: A classic example of directory entry
Author: eLDAP
In response to: LDAP Directory Object Model: rules of contents of an entry
Posted on: 08/09/2006 02:16:12 PM
Here is a classic directory entry
dn: uid=Babs_Jensen,ou=people,dc=mydomain,dc=com
uid: Babs_Jensen
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: inetOrgperson
cn: Babs Jensen
sn: Jensen
givenname: Barbara
mail: bjensen@example.com
In this structure, the structural object class
inetOrgperson inherits from structural
organizationalPerson, structural
person and eventually the abstract object class
top. Therefore, when you assign the
inetOrgperson object class to an entry, it automatically inherits the required and allowed attributes from the superior object class.
Here, 'objectClass' is the required attribute specified in
top while 'cn' and 'sn' are required attributes specified in
person. The rest attributes are defined in MAY lists of the objectclasses.
It should be noted that 'uid' is not required by schema itself, but it MIGHT be required to be present by RDN naming rule. Some LDAP servers, like SunOne and Active Directory, may automatically add the RDN as attribute when built up the entry.
>
> On 08/02/2006 06:36:19 PM
eLDAP wrote:
The directory object model allows an entry to be instantiated from several object classes with the followings rules:
Structural Auxiliary ... Auxiliary
| | |
----------------------------
|
Directory
Entry
An entry shall not belong only to abstract object classes;
An entry shall not belong to more than one structural object class (excluding its superclasses);
Besides being a member of the structural object class, an entry may be optionally a member of one or more auxiliary object classes.
References:
