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!

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

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

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...