Step 2. Configure Secure Connections to LDAP (Optional)
- LDAP over SSL (LDAPS)
- LDAPS uses SSL to encrypt LDAP connections. LDAPS uses the
ldaps://
scheme. - StartTLS
- StartTLS can wrap an unencrypted connection with TLS during the
connection process. This allows the same port to handle both unencrypted
and encrypted connections. StartTLS uses the
ldap://
scheme.
For either encryption method, if the LDAP server certificate is signed by a private Certificate Authority (CA) or not trusted by the default Java truststore, you must create a custom truststore file or modify a copy of the default Java truststore file to add the CA to the file. Then configure Data Collector to use the modified truststore file.
Use the same procedure to configure either secure method.
-
In the $SDC_CONF/ldap-login.conf file, set either the
useLdaps or useStartTLS
property to true.
By default, both properties are false and so Data Collector makes unencrypted connections to the LDAP server. If you set both properties to true, useStartTLS takes precedence.
-
Set the port property in the
ldap-login.conf file as required, based on the method
that you enabled:
- useLdaps - Use the port number for secure connections, typically 636.
- useStartTLS - Use the LDAP port number, typically 389.
-
If the LDAP server certificate is signed by a private CA or not trusted by the
default Java truststore, create a custom truststore file or modify a copy of the
default Java truststore file to add the CA to the file. Then configure Data Collector to use the modified truststore file.
By default, Data Collector uses the Java truststore file located in $JAVA_HOME/jre/lib/security/cacerts. If your certificate is signed by a CA that is included in the default Java truststore file, you do not need to create a truststore file and can skip this step.
In these steps, we show how to modify the default truststore file to add an additional CA to the list of trusted CAs. If you prefer to create a custom truststore file, see the keytool documentation.Note: If you've already configured Data Collector to use a custom truststore file to enable HTTPS, then simply add this additional CA to the same modified truststore file that you created in Step 2. Create a Truststore File. - Restart Data Collector to enable the changes.