Este contenido no está disponible en el idioma seleccionado.
Chapter 3. Requiring LDAPS or STARTTLS for encrypted connections
To prevent sending unencrypted passwords over the network, you can configure Directory Server to require users to use LDAPS or STARTTLS encryption when connecting to the server.
3.1. Configuring Directory Server using the command line to accept only connections encrypted with LDAPS or STARTTLS Copiar enlaceEnlace copiado en el portapapeles!
By default, Directory Server allows authentication using a bind DN and a password over unencrypted connections, which is a security risk. Suppose you cannot use an alternative secure mechanism, such as certificate-based authentication or SASL. In that case, you can configure Directory Server to require an encrypted connection when authenticating to the server using TLS or STARTTLS.
Requiring a secure connection for bind operations only applies to authenticated binds. Bind operations without a password, such as anonymous and unauthenticated binds, can proceed over standard connections.
Prerequisites
- You configured existing server-to-server connections, such as replication agreements, to use secure binds.
Procedure
Set the
nsslapd-require-secure-bindsconfiguration parameter toon:# dsconf -D "cn=Directory Manager" ldap://server.example.com config replace nsslapd-require-secure-binds=onOptional: If you want to use LDAPS, disable the plain text LDAP port:
# dsconf -D "cn=Directory Manager" ldap://server.example.com security disable_plain_portRestart the instance:
# dsctl instance_name restart
When you enable this feature, it is required for all connections. For example, this includes replication agreements, synchronization, and database chaining.
3.2. Configuring Directory Server using the web console to accept only connections encrypted with LDAPS or STARTTLS Copiar enlaceEnlace copiado en el portapapeles!
By default, Directory Server allows authentication using a bind DN and a password over unencrypted connections, which is a security risk. Suppose you cannot use an alternative secure mechanism, such as certificate-based authentication or SASL. In that case, you can configure Directory Server to require an encrypted connection when authenticating to the server using TLS or STARTTLS.
Requiring a secure connection for bind operations only applies to authenticated binds. Bind operations without a password, such as anonymous and unauthenticated binds, can proceed over standard connections.
Prerequisites
- You configured existing server-to-server connections, such as replication agreements, to use secure binds.
- You are logged in to the instance in the web console.
Procedure
-
Navigate to
, select the Require Secure Connectionsoption, and click . -
Optional: If you want to use LDAPS, navigate to
, and set LDAP Portto0to disable the plain text LDAP port. Click . -
Click in the top right corner, and select
Restart Instance.
When you enable this feature, it is required for all connections. For example, this includes replication agreements, synchronization, and database chaining.