Splunk Enterprise Security

Connection not secure : splunk web with https when using internal cert

Ksr1982
Explorer

My settings in web.conf

enableSplunkWebSSL = True
privKeyPath = /opt/splunk/etc/auth/myxxx/private.key
serverCert = /opt/splunk/etc/auth/myxxx/web.pem (conatins server cer, Intermediate ca and root ca)
requireClientCert = false

 

Getting error in browser > NET::ERR_CERT_COMMON_NAME_INVALID

splunkd.log

SSLCommon - Received fatal SSL3 alert. ssl_state='SSLv3 read client key exchange A', alert_description='certificate unknown'.
HttpListener - Socket error from x.x.x.x:xxxx while idling: error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown

 

All configuration seems correct. anyone resolved similar issue.

 

 

Labels (1)
Tags (2)

jackal713
Path Finder

Did you ever get any where on this issue?

I have the same symptom (NET::ERR_CERT_COMMON_NAME_INVALID) but I have a different error in my splunkd.log

Just in case anyone is wondering, the error I'm getting is "WARN HttpListener - Socket error from 127.0.0.1:6252 while idling: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number"

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


Introducing Unified TDIR with the New Enterprise Security 8.2

Read the blog

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

Get Updates on the Splunk Community!

Community Content Calendar, September edition

Welcome to another insightful post from our Community Content Calendar! We're thrilled to continue bringing ...

Splunkbase Unveils New App Listing Management Public Preview

Splunkbase Unveils New App Listing Management Public PreviewWe're thrilled to announce the public preview of ...

Leveraging Automated Threat Analysis Across the Splunk Ecosystem

Are you leveraging automation to its fullest potential in your threat detection strategy?Our upcoming Security ...