Splunk® Enterprise

Securing Splunk Enterprise

Download manual as PDF

This documentation does not apply to the most recent version of Splunk. Click here for the latest version.
Download topic as PDF

Secure SSO with TLS certificates

Configure the following SSL settings to enable Splunk Enterprise to perform TLS verification between Splunk Instance and the SOAP instance providing AttributeQuery service.

Unless noted, values not set default to the setting specified in server.conf.

[<saml-authSettings-key>]

sslVersions = <Comma-separated list of SSL versions to support>

sslCommonNameToCheck = <commonName> When populated, and 
sslVerifyServerCert is "true", splunkd limits most outbound HTTPS 
connections to hosts which use a cert with this common name. 

sslAltNameToCheck = <alternateName1>, <alternateName2>, ...If set, and 
sslVerifyServerCert' is "true", splunkd can verify certificates with 
"Subject Alternate Name" that matches any of the is alternate names in 
this list.

ecdhCurveName = <ECDH curve to use for ECDH key negotiation> 

serverCert = <Server certificate file> Default certificates, "sever.pem" are 
auto-generated by splunkd upon starting Splunk, you may replace the 
default cert with your own PEM format file.

sslPassword = <Server certificate password>

caCertFile = <Public key of the signing authority> The default value is cacert.pem 

caPath = <Path where all these certs are stored>. Default value is 
$SPLUNK_HOME/etc/auth

sslVerifyServerCert = [ true | false ] If true, distributed search makes a search 
request to another server in the search cluster. 

blacklistedAutoMappedRoles = <comma separated list of roles> Optionally provide a 
comma-separated list of Splunk roles that you do not want Splunk to auto-map if
received in the IDP Response.

blacklistedUsers = <comma separated list of user names> Optionally provide a
comma-separated list of user names that Splunk must reject from the IDP response.

nameIdFormat = <string> Optionally, and If supported by IDP,  specify the format of
the Subject returned in the SAML Assertion. 

ssoBinding = <HTTPPost | HTTPRedirect> Optionally specify the binding to use
when making a SP-initiated SAML request. The binding must match the one
configured on the IDP.

sloBinding = < <HTTPPost | HTTPRedirect> > Optionally specify the binding to
use when making a logout request or sending a logout response to complete 
the logout workflow. The binding must match the one configured on the IDP.

signatureAlgorithm = <RSA-SHA1 | RSA-SHA256> Optionally specify the signature
algorithm to user for a SP-initiated SAML request. 'signedAuthnRequest' must 
be set to true for this setting to take effect. The algorithm applies to both the  
http post and redirect binding.

replicateCertificates = <boolean> Optionally specify the IdP certificate files to 
replicate across search head cluster setup. Search head clustering must also 
be enabled. If certificate replication is not enabled, IdP certificate files must be 
replicated manually across SHC or verification of SAML signed assertions fails.

PREVIOUS
Configure SSO in CA siteminder
  NEXT
Configuring SAML in a search head cluster

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.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, 7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.0.7


Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters