An entry is unambiguously identified by a DN, which is the concatenation of selected attributes from each entry in the tree along a path leading from the root down to the named entry, ordered from right to left. For example, a DN for a user might look like this:
The allowable entries for the name are defined by the entry's
An LDAP client can bind to the directory (successfully log in) if it provides a user ID and password. The user ID must be a DN, the fully qualified list of names and attributes. This means that the user must provide a very long name.
Typically, the user knows only a simple user name (for example, the first
part of the DN above,
For more information, see
"
Some systems permit anonymous searches; others require a user DN and password. You can specify a user's DN and password for the search with the properties listed below. In addition, you can limit the scope of the search by specifying a filter (definition of the object class for the user) and a base (directory from which to begin the search) with the properties listed below.
Specifies the DN with which to bind (authenticate) to the server when searching for user DNs. This parameter is optional if anonymous access is supported by your server. If specified, this value must be a DN recognized by the directory service, and it must also have the authority to search for the entries.
If not set, it defaults to an anonymous search using the root DN specified
by the
Specifies the password to use for the guest user configured above to bind to
the directory service when looking up the DN. If not set, it defaults to an
anonymous search using the root DN specified by the
Specifies the root DN of the point in your hierarchy from which to begin a guest search for the user's DN. For example:
To narrow the search, you can specify a user's
Set
See the