Red Hat DIRECTORY SERVER 8.0 Command Reference Manual page 252

Glossary
authentication
authentication certificate
B
base DN
base distinguished name
bind DN
bind distinguished name
bind rule
branch entry
browser
browsing index
C
CA
cascading replication
242
(1) Process of proving the identity of the client user to the Directory
Server. Users must provide a bind DN and either the corresponding
password or certificate in order to be granted access to the directory.
Directory Server allows the user to perform functions or access files
and directories based on the permissions granted to that user by the
directory administrator.
client
(2) Allows a to make sure they are connected to a secure
server, preventing another computer from impersonating the server or
attempting to appear secure when it is not.
Digital file that is not transferable and not forgeable and is issued by a
third party. Authentication certificates are sent from server to client or
client to server in order to verify and authenticate the other party.
Base distinguished name. A search operation is performed on the
base DN, the DN of the entry and all entries below it in the directory
tree.
base DN.
See
Distinguished name used to authenticate to Directory Server when
performing an operation.
bind DN.
See
In the context of access control, the bind rule specifies the credentials
and conditions that a particular user or client must satisfy in order to
get access to directory information.
An entry that represents the top of a subtree in the directory.
Software, such as Mozilla Firefox, used to request and view World
Wide Web material stored as HTML files. The browser uses the HTTP
protocol to communicate with the host server.
Speeds up the display of entries in the Directory Server Console.
Browsing indexes can be created on any branch point in the directory
tree to improve display performance.
virtual list view index
See Also
Certificate Authority.
See
In a cascading replication scenario, one server, often called the hub
supplier, acts both as a consumer and a supplier for a particular
replica. It holds a read-only replica and maintains a changelog. It
receives updates from the supplier server that holds the master copy
of the data and in turn supplies those updates to the consumer.
.