Appendix D: Standards

 < Day Day Up > 



This section provides an overview of the most frequently used object classes and attribute types. The notation is the one used in the RFCs and in the OpenLDAP schema definitions. Different server implementations use other syntaxes for the definition of the schema elements; you will find more about different syntaxes in Chapter 3. For more in-depth information about object classes, attribute type definitions, and syntaxes, you can use the LDAP Schema Viewer available at http://ldap.akbkhome.com. The site's excellent design (maintained by Alan Knowles) makes it an invaluable tool for anyone needing to better understand the schema elements of LDAP.

Object Classes

 objectclass ( 2.5.6.1 NAME 'alias'    DESC 'RFC2256: an alias'    SUP top STRUCTURAL    MUST aliasedObjectName ) objectclass ( 2.5.6.2 NAME 'country'    DESC 'RFC2256: a country'    SUP top STRUCTURAL    MUST c    MAY ( searchGuide $ description ) ) objectclass ( 2.5.6.3 NAME 'locality'    DESC 'RFC2256: a locality'    SUP top STRUCTURAL    MAY ( street $ seeAlso $ searchGuide $ st $ 1 $ description ) ) objectclass ( 2.5.6.4 NAME 'organization'    DESC 'RFC2256: an organization'    SUP top STRUCTURAL    MUST o    MAY ( userPassword $ searchGuide $ seeAlso $    businessCategory $    x121Address $ registeredAddress $ destinationIndicator $    preferredDeliveryMethod $ telexNumber $    teletexTerminalIdentifier $    telephoneNumber $ internationaliSDNNumber $    facsimileTelephoneNumber $ street $ postOfficeBox $    postalCode $    postalAddress $ physicalDeliveryOfficeName $ st $ 1 $    description ) ) objectclass ( 2.5.6.5 NAME 'organizationalUnit'    DESC 'RFC2256: an organizational unit'    SUP top STRUCTURAL    MUST ou    MAY ( userPassword $ searchGuide $ seeAlso $    businessCategory $    x121Address $ registeredAddress $ destinationIndicator $    preferredDeliveryMethod $ telexNumber $    teletexTerminalIdentifier $    telephoneNumber $ internationaliSDNNumber $    facsimileTelephoneNumber $ street $ postOfficeBox $    postalCode $    postalAddress $ physicalDeliveryOfficeName $ st $ 1 $    description ) ) objectclass ( 2.5.6.6 NAME 'person'    DESC 'RFC2256: a person'    SUP top STRUCTURAL    MUST ( sn $ cn )    MAY ( userPassword $ telephoneNumber $ seeAlso $    description ) ) objectclass ( 2.5.6.7 NAME 'organizationalPerson'    DESC 'RFC2256: an organizational person'    SUP person STRUCTURAL    MAY ( title $ x121Address $ registeredAddress $    destinationIndicator $    preferredDeliveryMethod $ telexNumber $    teletexTerminalIdentifier $    telephoneNumber $ internationaliSDNNumber $    facsimileTelephoneNumber $ street $ postOfficeBox $    postalCode $    postalAddress $ physicalDeliveryOfficeName $ ou $ st $ 1 ) ) objectclass ( 2.5.6.9 NAME 'groupOfNames'    DESC 'RFC2256: a group of names (DNs)'    SUP top STRUCTURAL    MUST ( member $ cn )    MAY ( businessCategory $ seeAlso $ owner $ ou $ o $    description ) ) objectclass ( 2.5.6.10 NAME 'residentialPerson'    DESC 'RFC2256: an residential person'    SUP person STRUCTURAL    MUST 1    MAY ( businessCategory $ x121Address $ registeredAddress $    destinationIndicator $ preferredDeliveryMethod $    telexNumber $    teletexTerminalIdentifier $ telephoneNumber $    internationaliSDNNumber $    facsimileTelephoneNumber $ preferredDeliveryMethod $    street $    postOfficeBox $ postalCode $ postalAddress $    physicalDeliveryOfficeName $ st $ 1 ) ) objectclass ( 2.5.6.13 NAME 'dSA'    DESC 'RFC2256: a directory system agent (a server)'    SUP applicationEntity STRUCTURAL    MAY knowledgeInformation ) objectclass ( 2.5.6.14 NAME 'device'    DESC 'RFC2256: a device'    SUP top STRUCTURAL    MUST cn    MAY ( serialNumber $ seeAlso $ owner $ ou $ o $ 1 $    description ) ) objectclass ( 2.5.6.17 NAME 'groupOfUniqueNames'    DESC 'RFC2256: a group of unique names (DN and Unique    Identifier)'    SUP top STRUCTURAL    MUST ( uniqueMember $ cn )    MAY ( businessCategory $ seeAlso $ owner $ ou $ o $    description ) ) objectclass ( 1.3.6.1.4.1.250.3.15 NAME 'labeledURIObject'    DESC 'RFC2079: object that contains the URI attribute type'    MAY ( labeledURI )    SUP top AUXILIARY ) objectclass ( 1.3.6.1.4.1.1466.344 NAME 'dcObject'    DESC 'RFC2247: domain component object'    SUP top AUXILIARY MUST dc ) objectclass ( 1.3.6.1.1.3.1 NAME 'uidObject'    DESC 'RFC2377: uid object'    SUP top AUXILIARY MUST uid ) objectclass( 2.16.840.1.113730.3.2.2    NAME 'inetOrgPerson'    DESC 'RFC2798: Internet Organizational Person'    SUP organizationalPerson STRUCTURAL    MAY ( audio $ businessCategory $ carLicense $    departmentNumber $    displayName $ employeeNumber $ employeeType $    givenName $    homePhone $ homePostalAddress $ initials $ jpegPhoto $    labeledURI $ mail $ manager $ mobile $ o $ pager $    photo $ roomNumber $ secretary $ uid $ userCertificate $    x500uniqueIdentifier $ preferredLanguage $    userSMIMECertificate $ userPKCS12 )    ) 



 < Day Day Up > 



The ABCs of LDAP. How to Install, Run, and Administer LDAP Services
The ABCs of LDAP: How to Install, Run, and Administer LDAP Services
ISBN: 0849313465
EAN: 2147483647
Year: 2003
Pages: 149

Similar book on Amazon

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net