Netscape DIRECTORY SERVER 6.01 - DEPLOYMENT Deployment Manual page 68

Designing Your Directory Tree
You can avoid common name collisions by adding a unique identifier to the
common name. For example:
cn=Babs Jensen+employeeNumber=23,dc=example,dc=com
However, this can lead to awkward common names for large directories and can
be difficult to maintain.
A better method is to identify your person entries with some attribute other than
. Consider using one of the following attributes:
cn
•
uid
Use the
Possibilities include a user login ID or an employee number. A subscriber in a
hosting environment should be identified by the
•
mail
Use the
option can lead to awkward DNs that include duplicate attribute values (for
example:
use this option only if you cannot find some unique value that you can use
with the
of the
user IDs for temporary or contract employees.
•
employeeNumber
For employees of the
assigned attribute value such as
Whatever you decide to use for an attribute-data pair for person entry RDNs, you
should make sure that they are unique, permanent values. Person entry RDNs
should also be readable. For example,
preferable to
simplify some directory tasks, such as changing directory entries based on their
distinguished names. Also, some directory client applications assume that the
and
cn
Considerations for Person Entries in a Hosted Environment
If a person is a subscriber to a service, the entry should be of object class
and the entry should contain the
a customer subtree.
If a person is part of the hosting organization, represent them as an
with the
68 Netscape Directory Server Deployment Guide • January 2002
( ) attribute to specify some unique value of the person.
uid userID
attribute to contain the value for the person's email address. This
mail
mail=bjensen@example.com, dc=example,dc=com
attribute. For example, you would use the
uid
attribute if your enterprise does not assign employee numbers or
uid
inetOrgPerson
uid=b12r56A, dc=example,dc=com
attributes use human-readable names.
object class.
nsManagedPerson
uid
object class, consider using an employer
employeeNumber
uid=bjensen, dc=example,dc=com
because recognizable DNs
attribute. The attribute must be unique within
uid
attribute.
), so you should
attribute instead
mail
.
inetUser
inetOrgPerson
is
uid