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!

Event Series: Splunk Observability Metrics Cost Optimization

Balancing Scale and Spend: Gaining Control Over High-Volume Metrics in Splunk Observability Cloud As ...

Kick the Tires Before You Commit: A Hands-On Tour of the Splunk Observability Cloud ...

Evaluating an enterprise observability platform usually goes like this: fill out a form, get a free trial with ...

Deep insights, no barriers: Splunk Observability Cloud Free Edition

As software delivery cycles continue to accelerate, observability shouldn’t be a luxury — it should be a ...