About default certificate authentication
Splunk Enterprise 6.6 and higher includes certificates that are signed with Secure Hash Algorithm (SHA)-256 using a 2048-bit key. These certificates are part of a new installation of the software.
When you upgrade from a previous release, Splunk Enterprise replaces the existing cacert.pem.default and ca.pem.default Privacy Enhanced Mail (PEM) files. Upgrades do not affect existing certificates.
Because of the new default PEM format, you must upgrade all certificates and PEM files to SHA-256 using a 2048-bit key to avoid errors with validation. For example, indexers and forwarders might require updates to meet the same standards as Splunk Enterprise search heads. You might also want to check certificates for your license manager. If you do not update all certificates and PEM files, Splunk Enterprise logs the following error in splunkd.log when it attempts to connect to another instance over SSL:
ERROR TcpOutputFd - Connection to host=10.140.130.102:9997 failed. sock_error = 0. SSL Error = error:04091077:rsaroutines:INT_RSA_VERIFY:wrong signature length
| Securing Splunk Enterprise with FIPS | Harden the Splunk Enterprise installation directory on Windows |
This documentation applies to the following versions of Splunk® Enterprise: 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.2.10, 7.3.0, 7.3.1, 7.3.2, 7.3.3, 7.3.4, 7.3.5, 7.3.6, 7.3.7, 7.3.8, 7.3.9, 8.0.0, 8.0.1, 8.0.2, 8.0.3, 8.0.4, 8.0.5, 8.0.6, 8.0.7, 8.0.8, 8.0.9, 8.0.10, 8.1.0, 8.1.1, 8.1.2, 8.1.3, 8.1.4, 8.1.5, 8.1.6, 8.1.7, 8.1.8, 8.1.9, 8.1.10, 8.1.11, 8.1.12, 8.1.13, 8.1.14, 8.2.0, 8.2.1, 8.2.2, 8.2.3, 8.2.4, 8.2.5, 8.2.6, 8.2.7, 8.2.8, 8.2.9, 8.2.10, 8.2.11, 8.2.12, 9.0.0, 9.0.1, 9.0.2, 9.0.3, 9.0.4, 9.0.5, 9.0.6, 9.0.7, 9.0.8, 9.0.9, 9.0.10
Download manual
Feedback submitted, thanks!