On 05/12/14 09:30 -0400, Jignesh wrote:
I have confusion on on common name. In Open ldap it is a combination
first name and last name and other side it is unique. So it is forces us
to use something else then combination of first name and last name.
That's incorrect. The value can be anything that meets the syntax
constraints (see RFC 2256), and it "is typically the person's full name."
If you choose to use CN within the entry's DN, then you may well run into
conflicts with other entries. Consider using a uid, with a unique value,
Now tools like php openldap, apache directory shows the LDPA user in
navigation by common name. So if we map common name to something else then
we will have problem to view the list in these tools.
Make liberal use of search filters within client tools, such as apache
directory studio, to find particular entries (such as by common name). Of
course, if you actually have two people with the same name, then you'll
need to find your own method of distinguishing between them.
Is it possible to change the setting for above tools so that they can
reflect based on first name and last name instead of common name?
You also have other attributes to store partial, or whole, names into, such
as gecos and surname. Or you can create your custom attributes via schema