Table of Contents
Advertisement
Maintaining Consistent Schema
The following sections describe in detail how to maintain consistency within your
schema.
Schema Checking
Schema checking ensures that all new or modified directory entries conform to the
schema rules. When the rules are violated, the directory rejects the requested
change.
NOTE
By default, the directory enables schema checking. We do not recommend turning
it off. For information on turning schema checking on and off, see the Netscape
Directory Server Administrator's Guide.
With schema checking on, you must be attentive to required and allowed attributes
as defined by the object classes. Object class definitions usually contain at least one
required attribute, and one or more optional attributes. Optional attributes are
attributes that you are allowed, but not required, to add to the directory entry. If
you attempt to add an attribute to an entry that is neither required nor allowed
according to the entry's object class definition, then Directory Server returns an
object class violation message.
For example, if you define an entry to use the
then the
(you must specify values for these attributes when you create the entry). In
addition, there is a fairly long list of attributes that you can optionally use on the
entry. This list includes such descriptive attributes as
streetAddress
Selecting Consistent Data Formats
LDAP schema allow you to place any data that you want on any attribute value.
However, it is important to store data consistently in your directory tree by
selecting a format appropriate for your LDAP client applications and directory
users.
54
Netscape Directory Server Deployment Guide • May 2002
Schema checking checks only that the proper attributes are present.
It does not verify whether attribute values are in the correct syntax
for the attribute.
(
) and
commonName
cn
, and
userPassword
organizationalPerson
(
) attributes are required for the entry
surname
sn
.
object class,
,
telephoneNumber
uid
,
Advertisement
Table of Contents
