Getting Data In

Command-line syntax to deploy universal forwarder with SSL certificates?

vonStauf
Explorer

Based on the documentation provided, the proper command-line arguments to be used when deploying certificates is CERTFILE= ROOTCAFILE= CERTPASSWORD=. This syntax will copy the specified certificates to the Program Files\SplunkUniveralForwarder\ etc\auth folder, however the .conf file references the location where the certificate files came from and NOT the default \etc\auth folder. Since we are creating the images in a seperate environment, the result is a client configuration that looks for certificates on a network share that is unavailable, even though the installation copied them to its own \etc\auth folder. Is this something that can be corrected in the next build or am I missing a syntax on my command-line?

1 Solution

vonStauf
Explorer

-UPDATE-

Fixed the problem by manually creating the c:\Program Files\SplunkUniversalForwarder\etc\auth folder and then copying the cert.pem files to it prior to running the install. Then when the install is run, I reference the pem files in the etc\auth folder so that the conf files refer to the correct location. Its still a problem with the installation logic, but a workable enough solution.

View solution in original post

vonStauf
Explorer

-UPDATE-

Fixed the problem by manually creating the c:\Program Files\SplunkUniversalForwarder\etc\auth folder and then copying the cert.pem files to it prior to running the install. Then when the install is run, I reference the pem files in the etc\auth folder so that the conf files refer to the correct location. Its still a problem with the installation logic, but a workable enough solution.

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!

Make Your Machine Data AI-Ready in Splunk

Every team is getting ready for AI agents.   Thursday, November 12, 2026  |  11AM  PST / 2PM EST   ...

Splunk Asynchronous Forwarding Explained

Splunk asynchronous forwarding is often misunderstood as simply setting autoLBVolume. That is not quite right. ...

How to Monitor AI Agents with Splunk Agent Observability

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...