Splunk Enterprise

WARNING: Server Certificate Hostname Validation is disabled

BRFZ
Communicator

 

Hi Splunk Community,

I’ve generated self-signed SSL certificates and configured them in web.conf, but they don't seem to be taking effect. Additionally, I am receiving the following warning message when starting Splunk:

 
WARNING: Server Certificate Hostname Validation is disabled. Please see server.conf/[sslConfig]/cliVerifyServerName for details.


Could someone please help me resolve this issue? I want to ensure that Splunk uses the correct SSL certificates and that the hostname validation works properly.

Labels (2)
0 Karma

PickleRick
SplunkTrust
SplunkTrust

1. What do you mean by "they don't seem to be taking an effect"?

2. Did you verify with btool that the settings you've put into your configs are effective?

3. Did you restart Splunk?

4. Self-signed certs don't actually raise your level of security much. You should be using an external CA-issued certs (even if it's your own CA).

0 Karma

marnall
Motivator

Did you set cliVerifyServerName = true ? 

It would be helpful if you post your server.conf [sslConfig] stanza (sanitized if it contains sensitive information)

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Unlock What’s Next: The Splunk Cloud Platform at .conf25

In just a few days, Boston will be buzzing as the Splunk team and thousands of community members come together ...