LDAP System Administration [Electronic resources] نسخه متنی

4.3 Updating slapd.conf

Once the schema has been selected, the next step is to modify
slapd.conf to support the selected attribute
types and object classes. In order to support the
inetOrgPerson object class, you must include
inetorgperson.schema,
core.schema, and cosine.schema
in slapd.conf. The comments that begin
inetorgperson.schema outline the dependency on
the COSINE schema. Here are the modifications to the global section
of slapd.conf:

# /usr/local/etc/openldap/slapd.conf
# Global section
## Include the minimum schema required.
include         /usr/local/etc/openldap/schema/core.schema
## Added to support the inetOrgPerson object.
include         /usr/local/etc/openldap/schema/cosine.schema
include         /usr/local/etc/openldap/schema/inetorgperson.schema
## Added logging parameters
. . .

The database section is currently in working condition, so only a few
changes are needed. To better support
searches for employees, you should
modify the set of
indexes to include a more
complete list of attributes. In addition to creating an index for the
cn attribute, you'll also index
the surname (sn) and email address
(mail) attributes. In addition to the equality
(eq) index, you'll add a
substring (sub) index to support searches such
as "All employees whose last names begin with
C." Finally, you will add an equality index for the
departmentNumber attribute so that users can
search for employees within a given department. This index would not
be necessary if the directory were laid out as shown in Figure 4-2 because the same effect could be achieved by
beginning the search at the department ou. Here
are the changes to the database section:

## Indexes to maintain
index         objectClass         eq
index         cn,sn,mail          eq,sub
index         departmentNumber    eq
. . .

At this point, it's a good idea to verify that the
location specified by the directory parameter
exists and has the proper permissions. In our example, that directory
is /var/ldap/plainjoe.org. If this directory
does not exist, the following two commands ensure that the filesystem
is ready to store data:

root# mkdir -p /var/ldap/plainjoe.org
root# chmod 700 /var/ldap/plainjoe.org