Configure Splunk forwarding to use the default certificate

The default root certificate that ships with Splunk software is the same root certificate in every download. Splunk software uses these certificates by default and you should not need to configure them unless they have been removed or corrupted.

Default certificates are not considered highly secure. Anyone who has downloaded Splunk Enterprise has server certificates signed by the same root certificate and are able to authenticate to your certificates. To ensure that no one can easily snoop on your traffic or wrongfully send data to your indexers, we recommend that you replace them with signed certificates.

Important: The default certificates are set to expire three years after they are generated and new certificates must be created and configured at that time using one of the methods described in this manual.

Comments

The above example in this official documentation forwards encrypted traffic over TCP/9997. The examples in most unofficial documentation/guidance leave TCP/9997 for plaintext and specify TCP/9998 for TLS.

Just an observation that there's a mismatch.

Satyenshah

May 2, 2019

Bkessler, this is a great idea, I'll update the docs accordingly.

Ylechevallier, thanks for catching that, we've updated all of the docs to reflect the changes.

Jworthington splunk, Splunker

July 14, 2017

Since sslRootCAPath is not used on windows, as mentioned, docs should note how to achieve this using the depreciated settings:

caCertFile = cacert.pem
caPath = $SPLUNK_HOME\etc\auth

Bkessler splunk, Splunker

July 6, 2017

sslCertPath is deprecated in 6.5 and should be replaced by clientCert.

From outputs.conf.spec:
clientCert = <path>
* The full path to the client SSL certificate in PEM format.
* If (and only if) specified, this connection will use SSL.
* There is no default value.

Configure Splunk forwarding to use the default certificate

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

Send me a copy of this feedback

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

Feedback submitted, thanks!

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

Your Comment Has Been Posted Above

We use our own and third-party cookies to provide you with a great online experience. We also use these cookies to improve our products and services, support our marketing campaigns, and advertise to you on our website and other websites. Some cookies may continue to collect information after you have left our website.
Learn more (including how to update your settings) here »