Security

Port issue with splunkd SSL

irsysintegratio
Path Finder

Hello,

We want to enable Splunkd SSL, so we put
enableSplunkdSSL = true
to server.conf.
We generated a certificate using the FQDN as the CN of the certificate.

Then in our AddOn, we use splunk.getLocalServerInfo() to get the url:port. The problem is that splunk.getLocalServerInfo() always returns https://127.0.0.1:8089, even if we changed MgmtHostPort in web.conf. As a result, we always get an error:
SSLError: hostname '127.0.0.1' doesn't match xxxxxx, where xxxxxx is the CN we set for the certificate.

So how shall this work? Shall we use 127.0.0.1 as the CN to create a cert? Or we shall not call getLocalServerInfo()?

Thanks!

0 Karma
1 Solution

irsysintegratio
Path Finder

Ok, answering my own question. One way to contribute. 🙂

Need to set the following env var:
SPLUNKD_URI
to the FQDN of your machine. Then it will work.

View solution in original post

0 Karma

irsysintegratio
Path Finder

Ok, answering my own question. One way to contribute. 🙂

Need to set the following env var:
SPLUNKD_URI
to the FQDN of your machine. Then it will work.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...