Related Answers
Download topic as PDF
Secure LDAP with TLS certificates
Splunk uses OpenLDAP and OpenSSL. You can leverage both tools to secure your LDAP authentication with certificates. For more information on creating and managing certificates, see the OpenSSL documentation
The following examples are certificate configurations for LDAP. For more information about ways you can configure certificates in LDAP, see the OpenLDAP documentation at http://www.openldap.org/doc/admin24/tls.html:
LDAP server configuration
TLSCACertificateFile <filename>: the PEM-format file containing certificates for the CA's that
slapd will trust, including the certificate for the CA that signed the server certificate. Multiple
certificates can be appended to the file in no particular order.
TLSCertificateKeyFile <filename></code>: the file that contains the private key that matches
the certificate stored in the TLSCertificateFile file.
TLSCipherSuite <cipher-suite-spec>: ciphers will be accepted and the preference order.
<cipher-suite-spec> should be a cipher specification for OpenSSL. Use
"openssl ciphers -v ALL" for a list of available cipher specifications.
TLSRandFile <filename>: the file to obtain random bits from when /dev/urandom is not
available. If the system provides /dev/urandom then this option is not needed, otherwise
a source of random data must be configured.
TLSEphemeralDHParamFile <filename>: the file that contains parameters for
Diffie-Hellman ephemeral key exchange.
TLSVerifyClient { never | allow | try | demand }: specifies what checks to perform on client
certificates in an incoming TLS session, if any. This option is set to never by default, in
which case the server never asks the client for a certificate. LDAP client configuration
This directive specifies the file that contains the client certificate. This is a user-only directive and can only be specified in a user's .ldaprc file.
TLS_KEY <filename> specifies the file that contains the private key that matches the certificate
stored in the TLS_CERT file. The same constraints mentioned for TLSCertificateKeyFile apply here.
This is also a user-only directive.
TLS_RANDFILE <filename> the same as the server's TLSRandFile option.
TLS_REQCERT { never | allow | try | demand }
Note that if you host two or more LDAP servers, you may not want to use self-signed certificates, since each client will have to be configured to work with each certificate. In such a case it would be easier to create a certificate authority to sign your server certificates.
|
PREVIOUS LDAP prerequisites and considerations |
NEXT How Splunk Enterprise works with multiple LDAP servers |
This documentation applies to the following versions of Splunk® Enterprise: 6.5.0, 6.5.1, 6.5.1612 (Splunk Cloud only), 6.5.2, 6.5.3, 6.5.4, 6.5.5, 6.5.6, 6.5.7, 6.5.8, 6.5.9, 6.5.10, 6.6.0, 6.6.1, 6.6.2, 6.6.3, 6.6.4, 6.6.5, 6.6.6, 6.6.7, 6.6.8, 6.6.9, 6.6.10, 6.6.11, 6.6.12, 7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.0.7, 7.0.8, 7.0.9, 7.0.10, 7.0.11, 7.0.13, 7.1.0, 7.1.1, 7.1.2, 7.1.3, 7.1.4, 7.1.5, 7.1.6, 7.1.7, 7.1.8, 7.1.9, 7.1.10, 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6, 7.2.7, 7.2.8, 7.2.9, 7.3.0, 7.3.1, 7.3.2, 7.3.3, 7.3.4, 8.0.0, 8.0.1, 8.0.2
Feedback submitted, thanks!