Getting Data In

Support for multiple CA for universal forwarder to heavy forwarder connections

thscheidegger
Explorer

We are working with mutiple platforms that will send log data to heavy forwarders. We want to encrypt and if possible also authenticate the connetions. For one platform we have our own CA for the server certificates, the authenticated connections work, for the second platform we want to use the splunk certificates. I didn't see how we can configure the heavy forwarder with two different CAs. Is this even possible? How would I build this?

0 Karma

kenson
Explorer

You would define two different stanzas in inputs.conf on the heavyfwd boxes. Use port xxxx for CA1-signed clients and port yyyy for CA2-signed clients.

0 Karma

hettervik
SplunkTrust
SplunkTrust

Bump. The problem here is that even though you can define several [splunktcp-ssl] stanzas, you can only define one [SSL] stanza, apparently. I also want to define two [SSL] stanzas, for two different server certificates. Also, one of them would require client certificate, and the other would not. Is this possible?

EDIT: Got an answer to my own question here https://answers.splunk.com/answers/549719/two-ssl-certificates-on-a-single-indexer-forwarder.html

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 ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...