Netscape NETSCAPE DIRECTORY SERVER 6.1 - DEPLOYMENT Service manual

Schema Reference
Netscape Directory Server
Version6.1
August 2002

Netscape Communications Corporation ("Netscape") and its licensors retain all ownership rights to the software programs offered by
Netscape (referred to herein as "Software") and related documentation. Use of the Software and related documentation is governed
by the license agreement for the Software and applicable copyright law.
Your right to copy this documentation is limited by copyright law. Making unauthorized copies, adaptations or compilation works is
prohibited and constitutes a punishable violation of the law. Netscape may revise this documentation from time to time without
notice.
THIS DOCUMENTATION IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IN NO EVENT SHALL NETSCAPE BE
LIABLE FOR INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY KIND ARISING FROM ANY
ERROR IN THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION ANY LOSS OR INTERRUPTION OF BUSINESS,
PROFITS, USE, OR DATA.
The Software and documentation are copyright © 2001 Sun Microsystems, Inc. Portions copyright 1999, 2002 Netscape
Communications Corporation. All rights reserved.
Portions of the Software copyright © 1995 PEER Networks, Inc. All rights reserved. The Software contains the Taligent International
Classes from Taligent, Inc. and IBM Corp. Portions of the Software copyright ©1992-1998 Regents of the University of Michigan. All
rights reserved. The software contains encryption software from RSA Security Inc. Copyright © 1994 RSA Data Security, Inc. All
rights reserved.
Netscape and the Netscape N logo are registered trademarks of Netscape Communications Corporation in the United States and
other countries. Other Netscape logos, product names, and service names are also trademarks of Netscape Communications
Corporation, which may be registered in other countries. Other product and brand names are the exclusive property of their
respective owners.
The downloading, exporting, or reexporting of Netscape software or any underlying information or technology must be in full
compliance with all United States and other applicable laws and regulations. Any provision of Netscape software or documentation
to the U.S. government is with restricted rights as described in the license agreement for that Software.

3
Contents
PurposeofThisGuide ................................................................... 9
DirectoryServerOverview .............................................................. 10
ContentsofThisGuide ................................................................. 10
PrerequisiteReading ................................................................... 11
ConventionsUsedinThisBook .......................................................... 11
RelatedInformation .................................................................... 12
Chapter 1 AboutSchema ......................................................13
SchemaDefinition...................................................................... 13
ObjectClasses....................................................................... 14
RequiredandAllowedAttributes ................................................... 14
ObjectClassInheritance ........................................................... 14
Attributes .......................................................................... 15
AttributeSyntax .................................................................. 15
Single-ValuedandMulti-ValuedAttributes .......................................... 17
SchemaSupportedbyDirectoryServer6.x ................................................ 17
ObjectIdentifiers(OIDs) ................................................................ 19
ExtendingServerSchema ............................................................... 20
SchemaChecking ...................................................................... 20
Chapter 2 ObjectClassReference...............................................21
account ............................................................................... 22
alias .................................................................................. 23
cosClassicDefinition .................................................................... 24
cosDefinition .......................................................................... 25
cosIndirectDefinition ................................................................... 26
cosPointerDefinition.................................................................... 27
cosSuperDefinition ..................................................................... 28
cosTemplate........................................................................... 29
country ............................................................................... 30

4 Netscape Directory Server Schema Reference • August 2002
dcObject .............................................................................. 31
device ................................................................................ 32
document ............................................................................. 33
documentSeries ........................................................................ 35
domain ............................................................................... 36
domainRelatedObject................................................................... 38
dSA .................................................................................. 39
extensibleObject ....................................................................... 40
friendlyCountry ....................................................................... 41
groupOfCertificates .................................................................... 42
groupOfNames ........................................................................ 43
groupOfUniqueNames.................................................................. 44
groupOfURLs ......................................................................... 45
inetOrgPerson ......................................................................... 46
labeledURIObject ...................................................................... 49
locality ............................................................................... 50
newPilotPerson ........................................................................ 51
nsComplexRoleDefinition ............................................................... 53
nsFilteredRoleDefinition ................................................................ 54
nsLicenseUser ......................................................................... 55
nsManagedRoleDefinition............................................................... 56
nsNestedRoleDefinition................................................................. 57
nsRoleDefinition ....................................................................... 58
nsSimpleRoleDefinition ................................................................. 59
organization........................................................................... 60
organizationalPerson ................................................................... 62
organizationalRole ..................................................................... 64
organizationalUnit ..................................................................... 66
person ................................................................................ 68
pilotObject ............................................................................ 69
pilotOrganization ...................................................................... 70
residentialPerson....................................................................... 72
RFC822LocalPart....................................................................... 74
room ................................................................................. 76
strongAuthenticationUser ............................................................... 77
simpleSecurityObject ................................................................... 78
Chapter 3 AttributeReference ................................................. 79
abstract ............................................................................... 79
aliasedObjectName..................................................................... 79
associatedDomain...................................................................... 80
associatedName........................................................................ 80
audio ................................................................................. 81

5
authorCn ............................................................................. 81
authorSn .............................................................................. 82
authorityRevocationList................................................................. 82
buildingName . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
businessCategory ...................................................................... 83
c(countryName) ....................................................................... 83
cACertificate .......................................................................... 84
carLicense............................................................................. 84
certificateRevocationList ................................................................ 85
cn(commonName) ..................................................................... 85
co(friendlyCountryName) .............................................................. 86
cosAttribute ........................................................................... 86
cosIndirectSpecifier..................................................................... 87
cosPriority ............................................................................ 87
cosSpecifier ........................................................................... 87
cosTargetTree ......................................................................... 88
cosTemplateDn ........................................................................ 88
crossCertificatePair..................................................................... 88
dc(domainComponent)................................................................. 89
deltaRevocationList .................................................................... 89
departmentNumber .................................................................... 90
description ............................................................................ 90
destinationIndicator .................................................................... 91
displayName .......................................................................... 91
dITRedirect ........................................................................... 92
dmdName ............................................................................ 92
dn(distinguishedName) ................................................................ 92
dNSRecord............................................................................ 93
documentAuthor....................................................................... 93
documentIdentifier..................................................................... 94
documentLocation ..................................................................... 94
documentPublisher..................................................................... 95
documentStore ........................................................................ 95
documentTitle ......................................................................... 95
documentVersion ...................................................................... 96
drink(favouriteDrink) .................................................................. 96
dSAQuality ........................................................................... 97
employeeNumber ...................................................................... 97
employeeType ......................................................................... 98
enhancedSearchGuide .................................................................. 98
fax(fascimileTelephoneNumber)......................................................... 98
generationQualifier..................................................................... 99
givenName............................................................................ 99

6 Netscape Directory Server Schema Reference • August 2002
homePhone .......................................................................... 100
homePostalAddress ................................................................... 100
host ................................................................................. 101
houseIdentifier ....................................................................... 101
info ................................................................................. 102
initials ............................................................................... 102
internationalISDNNumber ............................................................. 102
janetMailbox ......................................................................... 103
jpegPhoto ............................................................................ 103
keyWords ............................................................................ 104
knowledgeInformation ................................................................ 104
l(localityName)....................................................................... 104
labeledURI ........................................................................... 105
lastModifiedBy ....................................................................... 105
lastModifiedTime ..................................................................... 106
mail ................................................................................. 106
mailPreferenceOption ................................................................. 107
manager ............................................................................. 107
member.............................................................................. 108
memberCertificateDescription .......................................................... 108
memberURL.......................................................................... 109
mobile ............................................................................... 109
name ................................................................................ 110
nsLicensedFor ........................................................................ 110
nsLicenseEndTime .................................................................... 111
nsLicenseStartTime.................................................................... 111
o(organizationName) ................................................................. 112
objectClass ........................................................................... 112
obsoletedByDocument ................................................................. 112
obsoletesDocument.................................................................... 113
organizationalStatus................................................................... 113
otherMailbox ......................................................................... 114
ou(organizationUnitName) ............................................................ 114
owner ............................................................................... 114
pager ................................................................................ 115
personalSignature..................................................................... 115
personalTitle ......................................................................... 116
photo................................................................................ 116
physicalDeliveryOfficeName ........................................................... 117
postalAddress ........................................................................ 117
postalCode ........................................................................... 118
postOfficeBox......................................................................... 118
preferredDeliveryMethod .............................................................. 118

7
preferredLanguage .................................................................... 119
presentationAddress .................................................................. 119
protocolInformation ................................................................... 120
ref................................................................................... 120
registeredAddress..................................................................... 120
roleOccupant ......................................................................... 121
roomNumber......................................................................... 121
searchGuide.......................................................................... 122
secretary ............................................................................. 122
seeAlso .............................................................................. 122
serialNumber......................................................................... 123
singleLevelQuality .................................................................... 123
sn(surname) ......................................................................... 124
st(stateOrProvinceName) .............................................................. 124
street ................................................................................ 125
subject ............................................................................... 125
subtreeMaximumQuality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
subtreeMinimumQuality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
supportedAlgorithms.................................................................. 126
supportedApplicationContext .......................................................... 127
telephoneNumber..................................................................... 127
teletexTerminalIdentifier ............................................................... 127
telexNumber ......................................................................... 128
textEncodedORAddress................................................................ 128
title.................................................................................. 129
ttl(timeToLive) ....................................................................... 129
uid(userID) .......................................................................... 130
uniqueIdentifier ...................................................................... 130
uniqueMember . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
updatedByDocument .................................................................. 131
updatesDocument..................................................................... 131
userCertificate ........................................................................ 132
userClass ............................................................................ 132
userPassword ........................................................................ 133
userPKCS12 .......................................................................... 133
userSMIMECertificate ................................................................. 134
x121Address ......................................................................... 134
x500UniqueIdentifier .................................................................. 134
Chapter 4 Operational Attributes, Special Attributes, and Special Object Classes . . . . . . 137
OperationalAttributes ................................................................. 137
accountUnlockTime ................................................................... 137
aci .................................................................................. 138

8 Netscape Directory Server Schema Reference • August 2002
altServer ............................................................................. 138
attributeTypes ........................................................................ 139
copiedFrom .......................................................................... 139
copyingFrom ......................................................................... 139
dITContentRules...................................................................... 140
dITStructureRules..................................................................... 140
ldapSyntaxes ......................................................................... 141
matchingRules........................................................................ 141
matchingRuleUse ..................................................................... 141
nameForms .......................................................................... 142
namingContexts ...................................................................... 142
nsds5replconflict ...................................................................... 143
nsRole ............................................................................... 143
nsRoleDn ............................................................................ 143
numSubordinates ..................................................................... 144
objectClasses ......................................................................... 145
passwordAllowChangeTime ........................................................... 145
passwordExpirationTime .............................................................. 145
passwordExpWarned.................................................................. 146
passwordHistory...................................................................... 146
passwordRetryCount .................................................................. 146
retryCountResetTime .................................................................. 147
subschemaSubentry ................................................................... 147
supportedControl ..................................................................... 148
supportedExtension ................................................................... 148
supportedLDAPVersion ............................................................... 148
supportedSASLMechanisms ............................................................ 149
SpecialAttributes ..................................................................... 149
changes .............................................................................. 149
changeLog ........................................................................... 150
changeNumber ....................................................................... 150
changeTime .......................................................................... 150
changeType .......................................................................... 151
deleteOldRdn......................................................................... 151
newRdn ............................................................................. 151
newSuperior.......................................................................... 152
targetDn ............................................................................. 152
SpecialObjectClasses.................................................................. 153
changeLogEntry ...................................................................... 153
passwordObject....................................................................... 154
subschema ........................................................................... 155
Index ....................................................................... 157

9
About This Reference Guide
Netscape Directory Server (Directory Server) 6.x is a powerful and scalable
distributed directory server based on the industry-standard Lightweight Directory
Access Protocol (LDAP). Directory Server is the cornerstone for building a
centralized and distributed data repository that can be used in your intranet, over
your extranet with your trading partners, or over the public Internet to reach your
customers.
This preface contains the following sections:
• Purpose of This Guide (page 9)
• Directory Server Overview (page 10)
• Contents of This Guide (page 10)
• Prerequisite Reading (page 11)
• Conventions Used in This Book (page 11)
• Related Information (page 12)
Purpose of This Guide
This Schema Reference guide describes the standard directory schema for Directory
Server, and lists all the object classes and attributes defined by the standard
schema. The information provided here is intended for the administrator who
manages and maintains the schema.

Directory Server Overview
10 Netscape Directory Server Schema Reference • August 2002
Directory Server Overview
The major components of Directory Server include:
• An LDAP server—The core of the directory service, provided by the ns-slapd
daemon, and compliant with the LDAP v3 Internet standards.
• Directory Server Console—An improved management console that
dramatically reduces the effort of setting up and maintaining your directory
service. The Directory Server Console is part of Netscape Console, the common
management framework for Netscape servers.
• SNMP Agent—Permits you to monitor your directory server in real time using
the Simple Network Management Protocol (SNMP).
• Online backup and restore—Allows you to create backups and restore from
backups while the server is running.
Contents of This Guide
Chapter 1, “About Schema” provides an overview of some of the basic concepts of
the directory schema, and lists the files in which the schema is described. It
describes object classes, attributes and Object Identifiers (OIDs), and briefly
discusses schema checking and extending server schema.
Chapter 2, “Object Class Reference” contains an alphabetical list of the object
classes accepted by the default schema. It gives a definition of each object class, and
gives the list of required and allowed attributes specific to the particular object
class. However, any mandatory and optional attributes inherited from superior
object classes are not listed.
Chapter 3, “Attribute Reference” contains an alphabetic list of the standard
attributes. It gives a definition of each attribute, and gives the attribute syntax.
Chapter 4, “Operational Attributes, Special Attributes, and Special Object
Classes” contains operational attributes used by Directory Server. The chapter also
describes some special attributes and object classes that are used by the server.

Prerequisite Reading
About This Reference Guide 11
Prerequisite Reading
This guide describes the standard schema and the standard object classes and
attributes. However, this guide does not describe how to design, customize or
maintain your schema, nor does it give any information on replication. Those
concepts are described in the Netscape Directory Server Deployment Guide.You
should read that book before continuing with this manual.
When you are familiar with directory server schema concepts, and have done some
preliminary planning for your directory service, you can install the Directory
Server. The instructions for installing the various Directory Server components are
contained in the Netscape Directory Server Installation Guide.
Preliminary planning includes deciding how to represent the data you store. You
should chose predefined schema elements to meet as many of your needs as
possible. These predefined schema elements are listed in this guide.
Conventions Used in This Book
This section explains the conventions used in this book.
Monospaced font—Thistypefaceisusedforanytextthatappearsonthecomputer
screen or text that you should type. It is also used for filenames, functions, and
examples.
Throughout this book you will see path references of the form:
serverRoot/slapd-serverID/...
serverRoot is the installation directory. For Directory Server 5.x and 6.x,
/usr/netscape/servers is the default installation directory on UNIX. On
Windows, it is c:\usr\netscape\servers. If you have installed Directory
Server in a different location, you should adapt the path accordingly.
serverID is the ID or identifier you assigned to an instance of Directory Server
when you installed it. For example, if you gave the server an identifier of
phonebook, then the actual path would look like this:
/usr/netscape/servers/slapd-phonebook/. . .
All paths specified in this manual are in UNIX format. If you are using a
Windows-based Directory Server, you should assume the equivalent file paths
whenever UNIX file paths are shown in this book.

Related Information
12 Netscape Directory Server Schema Reference • August 2002
In examples/sample code, paths assume that the Directory Server is installed in the
default location /usr/netscape/servers. If you have installed your Directory
Server in a different location, adapt the paths accordingly. Also, all examples use
phonebook for the server identifier where appropriate.
Related Information
The document set for Directory Server also contains the following guides:
•Netscape Directory Server Installation Guide. Procedures for installing your
Directory Server as well as procedures for migrating your Directory Server.
•Netscape Directory Server Deployment Guide. Provides an overview for planning
your deployment of the Directory Server. Includes deployment examples.
•Netscape Directory Server Administrator’s Guide. Procedures for the day-to-day
maintenance of your directory server. Includes information on configuring
server-side plug-ins.
•Netscape Directory Server Configuration, Command, and File Reference.
Information about the command-line scripts, configuration attributes, and log
files shipped with Directory Server.
•Netscape Directory Server Plug-In Programmer’s Guide. Describes how to write
server plug-ins in order to customize and extend the capabilities of Directory
Server.
For a list of documentation installed with Directory Server, open the
<server_root>/manual/en/slapd/index.htm file, where <server_root> is the
directory in which you installed Directory Server.
For the latest information about Directory Server, including current release notes,
complete product documentation, technical notes, and deployment information,
checkthissite:http://enterprise.netscape.com/docs

13
Chapter 1
About Schema
This chapter provides an overview of some of the basic concepts of the directory
schema, and lists the files in which the schema is described. It describes object
classes, attributes and object identifiers (OIDs), and briefly discusses extending
server schema and schema checking.
This chapter contains the following sections:
• Schema Definition (page 13)
• Schema Supported by Directory Server 6.x (page 17)
• Object Identifiers (OIDs) (page 19)
• Extending Server Schema (page 20)
• Schema Checking (page 20)
Schema Definition
The directory schema is a set of rules that defines how the data can be stored in the
directory. The data is stored in the form of directory entries. Each entry is a set of
attributes and their values. Each entry must have an object class. The object class
specifies the kind of object the entry describes and defines the set of attributes it
contains. The schema defines the type of entries allowed, their attribute structure
and the syntax of the attributes.The schema can be modified and extended if it does
not meet your required needs.
To find detailed information about object classes, attributes, and how the Netscape
Directory Server (Directory Server) uses the schema, refer to the Netscape Directory
Server Deployment Guide.

Schema Definition
14 Netscape Directory Server Schema Reference • August 2002
Object Classes
In LDAP, an object class defines the set of attributes that can be used to define an
entry. The LDAP standard provides some basic types of object classes, including:
• Groups, including unordered lists of individual objects or groups of objects.
• Locations, such as the country name and description.
• Organizations.
• People.
• Devices.
Required and Allowed Attributes
Every object class includes a number of required attributes and of allowed
attributes. Required attributes include the attributes that must be present in entries
using the object class. All entries require the objectClass attribute, which defines
the object classes assigned to the entry.
Allowed attributes include the attributes that may be present in entries using the
object class.
Example: Object Class = person
Required Attributes
object class
cn (common name)
sn (surname)
Allowed Attributes
description
seeAlso
telephoneNumber
userPassword
Object Class Inheritance
An entry can have more than one object class. For example, the entry for a person is
defined by the person object class, but may also be defined by attributes in the
inetOrgPerson,groupOfNames,andorganization object classes.

Schema Definition
Chapter 1 About Schema 15
The server’s object class structure determines the list of required and allowed
attributes for a particular entry. For example, a person entry is usually defined
with the following object class structure:
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: inetOrgperson
In this structure, the inetOrgperson inherits from the organizationalPerson and
person object classes. Therefore, when you assign the inetOrgperson object class
to an entry, it automatically inherits the required and allowed attributes from the
superior object class.
Attributes
Directory data is represented as attribute-value pairs. Any piece of information in
the directory is associated with a descriptive attribute.
For instance, the commonName,orcn, attribute is used to store a person’s name. A
person named Jonas Salk can be represented in the directory as
cn: Jonas Salk
Each person entered in the directory can be defined by the collection of attributes
in the inetorgperson object class. Other attributes used to define this entry could
include:
givenname: Jonas
surname: Salk
mail: [email protected]
Attribute Syntax
Each attribute has a syntax definition that describes the type of information
provided by the attribute.
Attribute syntax is used by the Directory Server to perform sorting and pattern
matching.
Table 1-1 lists the different syntax methods that can be applied to attributes, and
gives an OID and a definition for each syntax method.

Schema Definition
16 Netscape Directory Server Schema Reference • August 2002
Table 1-1 Attribute Syntax
Syntax Method OID Definition
Binary 1.3.6.1.4.1.1466.115.121.1.5 Indicates that values for this attribute are binary
Boolean 1.3.6.1.4.1.1466.115.121.1.7 Indicates that this attribute has one of only two
values: True or False
Country String 1.3.6.1.4.1.1466.115.121.1.11 Indicates that values for this attribute are limited
to exactly two printable string characters, for
example US
DN 1.3.6.1.4.1.1466.115.121.1.12 Indicates that values for this attribute are DNs.
DirectoryString 1.3.6.1.4.1.1466.115.121.1.15 Indicates that values for this attribute are not
case sensitive
GeneralizedTime 1.3.6.1.4.1.1466.115.121.1.24 Indicates that values for this attribute are
encoded as printable strings. The time zone
must be specified. It is strongly recommended to
use GMT time.
IA5String 1.3.6.1.4.1.1466.115.121.1.26 Indicates that values for this attribute are case
sensitive.
INTEGER 1.3.6.1.4.1.1466.115.121.1.27 Indicates that valid values for this attribute are
numbers.
OctetString 1.3.6.1.4.1.1466.115.121.1.40 Same behavior as binary
Postal Address 1.3.6.1.4.1.1466.115.121.1.41 Indicates that values for this attribute are
encoded according to
postal-address = dstring * (“$”
dstring)
where each dstring component is encoded as a
value of type DirectoryString syntax.
Backslashes and dollar characters, if they occur,
are quoted, so that they will not be mistaken for
line delimiters. Many servers limit the postal
address to 6 lines of up to thirty characters. For
example:
1234 Main St.$Anytown, TX 1234$USA
TelephoneNumber 1.3.6.1.4.1.1466.115.121.1.50 Indicates that values for this attribute are in the
form of telephone numbers. It is recommended
to use telephone numbers in international form

Schema Supported by Directory Server 6.x
Chapter 1 About Schema 17
Single-Valued and Multi-Valued Attributes
By default, most attributes are multi-valued. This means that an entry can contain
the same attribute with multiple values. For example, cn,tel and object class
are all attributes that can have more than one value. Attributes that are
single-valued—that is, only one instance of the attribute can be specified—are
noted as such. For example, uidNumber can only have one possible value.
Schema Supported by Directory Server 6.x
The schema provided with Directory Server 6.x is described in a set of files stored
in the serverRoot/slapd-serverID/config/schema directory.
You can modify the schema by creating new object classes and attributes. These
modifications are stored in a separate file called 99user.ldif. You should not
modify the standard files provided with the Directory Server, because you incur
the risk of breaking compatibility with other Netscape products, or of causing
interoperability problems with directory servers from vendors other than Netscape
Communications Corporation.
For more information about how the Directory Server stores information and
suggestions for planning directory schema, refer to the Netscape Directory Server
Deployment Guide.
The following tables list the schema files that are provided with Directory Server.
Table 1-2 lists the schema files that are used by the Directory Server. Table 1-3 lists
the schema files that are used by other Netscape products.
URI Indicates that the values for this attribute are in
the form of a URL, introduced by a string such
as http://,https://,ftp://,ldap://,
and ldaps://. The URI has the same behavior
as IA5String. See RFC 2396.
Table 1-1 Attribute Syntax (Continued)
Syntax Method OID Definition

Schema Supported by Directory Server 6.x
18 Netscape Directory Server Schema Reference • August 2002
Table 1-2 Schema Files used by Directory Server
Schema Filename Purpose
00core.ldif Recommended core schema from the X.500 and LDAP
standards(RFCs),andschemausedbytheDirectory
Server itself.
05rfc2247.ldif Schema from RFC 2247 and related pilot schema
“Using Domains in LDAP/X.500 Distinguished
Names.”
05rfc2927.ldif Schema from RFC 2927 “MIME Directory Profile for
LDAP Schema.”
10presence.ldif Schema for Presence information; the file lists the
default object classes with the allowed attributes that
must be added to a user’s entry in order for
instant-messaging presence information to be
available for that user.
10rfc2307.ldif Schema from RFC 2307 “An Approach for Using
LDAP as a Network Information Service.”
20subscriber.ldif Common schema elements for Netscape-Nortel
subscriber interoperability.
25java-object.ldif Schema from RFC 2713 “Schema for Representing
Java(tm) Objects in an LDAP Directory.”
28pilot.ldif Schema from the pilot RFCs, especially RFC 1274, that
is no longer recommended by Netscape for use in new
deployments.
30ns-common.ldif Common Netscape schema.
50ns-directory.ldif Additional schema used by Directory Server 4.x.
50ns-value.ldif Netscape servers “value item” schema.
99user.ldif Customer modifications to the schema.
Table 1-3 Schema Files used by other Netscape Products
Schema Filenames Purpose
50netscape-servicemgt.ldif Netscape service management schema elements.
50ns-admin.ldif Schema used by Netscape Administration Server.
50ns-calendar.ldif Netscape Calendar Server schema.

Object Identifiers (OIDs)
Chapter 1 About Schema 19
Object Identifiers (OIDs)
Object identifiers (OIDs) are assigned to all attributes and object classes to conform
to the LDAP and X.500 standards. An OID is a sequence of integers, typically
written as a dot-separated string. When no OID is specified, the Directory Server
automatically uses ObjectClass_name-oid and attribute_name-oid.
TheNetscapebaseOIDis
2.16.840.1.113730
The base OID for the Directory Server is
50ns-certificate.ldif Schema for Netscape Certificate Management System.
50ns-compass.ldif Schema for the Netscape Compass Server.
50ns-delegated-admin.ldif Schema for Netscape Delegated Administrator 4.5.
50ns-legacy.ldif Legacy Netscape Schema.
50ns-mail.ldif Schema for Netscape Messaging Server.
50ns-mcd-browser.ldif Schema for Netscape Mission Control Desktop - Browser.
50ns-mcd-config.ldif Schema for Netscape Mission Control Desktop -
Configuration.
50ns-mcd-li.ldif Schema for Netscape Mission Control Desktop - Location
Independence.
50ns-mcd-mail.ldif Schema for Netscape Mission Control Desktop - Mail.
50ns-media.ldif Schema for Netscape Media Server.
50ns-mlm.ldif Schema for Netscape Mailing List Manager.
50ns-msg.ldif Schema for Netscape Web Mail.
50ns-netshare.ldif Schema for Netscape Netshare.
50ns-news.ldif Schema for Netscape Collabra Server.
50ns-proxy.ldif Schema for Netscape Proxy Server.
50ns-wcal.ldif Schema for Netscape Web Calendaring.
50ns-web.ldif Schema for Netscape Web Server.
51ns-calendar.ldif Schema for Netscape Calendar Server.
Table 1-3 Schema Files used by other Netscape Products (Continued)
Schema Filenames Purpose

Extending Server Schema
20 Netscape Directory Server Schema Reference • August 2002
2.16.840.1.113730.3
All Netscape-defined attributes have the base OID of
2.16.840.1.113370.3.1
All Netscape-defined object classes have the base OID of
2.16.840.1.113730.3.2
For more information about OIDs or to request a prefix for your enterprise, please
go to the Internet Assigned Number Authority (IANA) web site at
http://www.iana.org/.
Extending Server Schema
The Directory Server schema includes hundreds of object classes and attributes that
can be used to meet most of your requirements. This schema can be extended with
new object classes and attributes that meet evolving requirements for the directory
service in the enterprise.
When adding new attributes to the schema, a new object class should be created to
contain them (adding a new attribute to an existing object class can compromise
the Directory Server’s compatibility with existing LDAP clients that rely on the
standard LDAP schema and may cause difficulties when upgrading the server).
For more information about extending server schema, refer to the Netscape
Directory Server Deployment Guide.
Schema Checking
You should run Directory Server with schema checking turned on.
The schema checking capability of Directory Server checks entries when you add
them to the directory or when you modify them, to verify that:
• Object classes and attributes used in the entry are defined in the directory
schema
• Attributes required for an object class are contained in the entry
• Only attributes allowed by the object class are contained in the entry
Schema checking also occurs when importing a database using LDIF. For more
information, refer to the Netscape Directory Server Administrator’s Guide.