Why are there different names for inputs.conf and outputs.conf?

[ddrillic]

On the outputs.conf of the forwarder we use sslPassword, sslCertPath and sslRootCAPath while the inputs.conf refers to the same exact configurations via password, serverCert and rootCA.

Why is that?

[ddrillic]

Interesting to see this thread What is the most simple way to enable SSL communication between my forwarders and indexers?

It shows -

[jworthington_sp · Accepted solution]

Hi ddrillic,

You are definitely looking at an old version of the spec files. Are you working with a version of Splunk that is earlier than 6.4?

In the later versions of Splunk:

• "sslCertPath" is deprecated, we now use "clientCert" instead
• "sslRootCAPath" has been deprecated entirely.

In inputs.conf

• "rootCA" is deprecated.

I do think there are probably some things we can do to make the files more compatible, I'm working with dev on that. Thank you for bringing this up.

Thanks,
jen

[ddrillic]

Much appreciated Jen.

[ddrillic]

Really interesting as I took the Admin 7.0 class in March and in the associated pdf we see -

[jworthington_sp]

Interesting! I will reach out to education and see what is going on.

[ddrillic]

Thank you @jworthington - let's please keep in mind that the pdfs for the various classes are sensational ; -)

[ddrillic]

For the record, we are "stuck" here in our place with sslCertPath for backward compatibility since we still have forwarders older than 6.5.2. They will not work with clientCert.