Novell LINUX ENTERPRISE SERVER 10 - INSTALLATION AND ADMINISTRATION 11-05-2007, Installation Manual

Page: 683 / 982

Table 36.1 Commonly Used Object Classes and Attributes
Required At-
tributes Example En-
try Meaning Object Class
dc example domainComponent (name
components of the domain) dcObject
ou doc organizationalUnit (organiza-
tional unit) organizationalU-
nit
sn and cn Geeko Linux inetOrgPerson (person-related
data for the intranet or Internet) inetOrgPerson
Example 36.1, “Excerpt from schema.core ” (page 665) shows an excerpt from a scheme
directive with explanations (line numbering for explanatory reasons).
Example 36.1 Excerpt from schema.core
#1 attributetype (2.5.4.11 NAME ( 'ou' 'organizationalUnitName')
#2 DESC 'RFC2256: organizational unit this object belongs to'
#3 SUP name )
...
#4 objectclass ( 2.5.6.5 NAME 'organizationalUnit'
#5 DESC 'RFC2256: an organizational unit'
#6 SUP top STRUCTURAL
#7 MUST ou
#8 MAY (userPassword $ searchGuide $ seeAlso $ businessCategory
$ x121Address $ registeredAddress $ destinationIndicator
$ preferredDeliveryMethod $ telexNumber
$ teletexTerminalIdentifier $ telephoneNumber
$ internationaliSDNNumber $ facsimileTelephoneNumber
$ street $ postOfficeBox $ postalCode $ postalAddress
$ physicalDeliveryOfficeName
$ st $ l $ description) )
...
The attribute type
organizationalUnitName
and the corresponding object class
organizationalUnit
serve as an example here. Line 1 features the name of the
attribute, its unique OID (object identifier) (numerical), and the abbreviation of the at-
tribute.
LDAP—A Directory Service 665