HP-UX Directory Server 8.1 deployment guide

8.4.3 Certificate-based authentication
An alternative form of directory authentication involves using digital certificates to bind to the
directory. The directory prompts users for a password when they first access it. However, rather
than matching a password stored in the directory, the password opens the user's certificate
database.
If the user supplies the correct password, the directory client application obtains authentication
information from the certificate database. The client application and the directory then use this
information to identify the user by mapping the user's certificate to a directory DN. The directory
allows or denies access based on the directory DN identified during this authentication process.
For more information about certificates and SSL, see the Administrator's Guide.
8.4.4 Simple password over SSL/TLS
When a secure connection is established between Directory Server and a client application using
SSL or the Start TLS operation, the server can demand an extra level of authentication by
requesting a password. In such cases, the password is not transmitted in plain text.
For more information about SSL, see “Securing server to server connections”. For information
about the Start TLS operation, refer to the Administrator's Guide.
8.4.5 Simple authentication and security layer
A method for adding authentication support to connection-based protocols. Especially useful in
conjunction with Kerberos, allow the use of Kerberos credentials to authenticate to the directory.
8.4.6 Proxy authentication
Proxy authentication is a special form of authentication because the user requesting access to the
directory does not bind with its own DN but with a proxy DN.
The proxy DN is an entity that has appropriate rights to perform the operation requested by the
user. When proxy rights are granted to a person or an application, they are granted the right to
specify any DN as a proxy DN, with the exception of the Directory Manager DN.
One of the main advantages of proxy right is that an LDAP application can be enabled to use a
single thread with a single bind to service multiple users making requests against the Directory
Server. Instead of having to bind and authenticate for each user, the client application binds to
the Directory Server using a proxy DN.
The proxy DN is specified in the LDAP operation submitted by the client application. For example:
ldapmodify -D "cn=directory manager" -w secret -p 389 \
-D "cn=directory manager" -w secret -p 389 -h server.example.com \
-Y "cn=joe, dc=example,dc=com" -f mods.ldif
This ldapmodify command gives the manager entry (cn=Directory Manager) the permissions
of a user named Joe (cn=joe) to apply the modifications in the mods.ldif file. The manager
does not need to provide Joe's password to make this change.
108 Designing a secure directory