Security

useSSL doesn't seem to work in 8.0.2.1

agitelzon
Explorer

I am trying to set up my forwarders to use SSL without having to use the built in client certs on version 8.0.2.1. It looks like the option useSSL in the outputs.conf file doesn't do what the documentation says.

In https://docs.splunk.com/Documentation/Splunk/8.0.2/Admin/Outputsconf it says

    * Whether or not the forwarder uses SSL to connect to the receiver, or relies
      on the 'clientCert' setting to be active for SSL connections.
    * If set to "true", then the forwarder uses SSL to connect to the receiver.
    * Default: legacy

Here is my outputs.conf file

[tcpout]
defaultGroup = default-autolb-group

[tcpout:default-autolb-group]
server = splunkserver:9997
useSSL = true

Here is the inputs.conf file on the server

[splunktcp-ssl://9997]
connection_host = ip

[SSL]
requireClientCert = false
serverCert = $SPLUNK_HOME/etc/auth/servercert.pem
#Use sslPassword = password
sslPassword = password

This outputs.conf file does work

[tcpout]
defaultGroup = default-autolb-group

[tcpout:default-autolb-group]
server = splunkserver:9997
useSSL = true
clientCert = $SPLUNK_HOME/etc/auth/server.pem
sslPassword = password
Labels (1)
Tags (2)
0 Karma

agudla
New Member

i am also facing same issue. useSSL is not being honoured, we are getting error "rror encountered for connection from src=<IP>:34818. error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol

Tags (1)
0 Karma
Get Updates on the Splunk Community!

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics GA in US-AWS!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...