Naming Entries - Red Hat DIRECTORY SERVER 7.1 - DEPLOYMENT Deployment Manual

Table of Contents

Advertisement

You can set access controls based on the directory content rather than the directory
tree. The ACI filtered target mechanism lets you define a single access control rule
stating that a directory entry has access to all entries containing a particular
attribute value. For example, you could set an ACI filter that gives the sales
administrator access to all the entries containing the attribute
However, ACI filters can be difficult to manage. You must decide which method of
access control is best suited to your directory: organizational branching in your
directory tree hierarchy, ACI filters, or a combination of the two.

Naming Entries

After designing the hierarchy of your directory tree, you need to decide which
attributes to use when naming the entries within the structure. Generally, names
are created by choosing one or more of the attribute values to form a relative
distinguished name (RDN). The RDN is the left-most DN attribute value. The
attributes you use depend on the type of entry you are naming.
Your entry names should adhere to the following rules:
The attribute you select for naming should be unlikely to change.
The name must be unique across your directory.
A unique name ensures that a DN can refer to at most one entry in your directory.
When creating entries, define the RDN within the entry. By defining at least the
RDN within the entry, you can locate the entry more easily. This is because
searches are not performed against the actual DN but rather the attribute values
stored in the entry itself.
Attribute names have a meaning, so try to use the attribute name that matches the
type of entry it represents. For example, do not use
organization, or
c (country)
The following sections provide tips on naming entries:
Naming Person Entries
Naming Group Entries
Naming Organization Entries
Naming Other Kinds of Entries
to represent an organizational unit.
Chapter 4
Designing Your Directory Tree
.
ou=Sales
to represent an
l (locality)
Designing the Directory Tree
71

Advertisement

Table of Contents
loading

This manual is also suitable for:

Directory server 7.1

Table of Contents