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.

Get Updates on the Splunk Community!

Archived Metrics Now Available for APAC and EMEA realms

We’re excited to announce the launch of Archived Metrics in Splunk Infrastructure Monitoring for our customers ...

Detecting Remote Code Executions With the Splunk Threat Research Team

WATCH NOWRemote code execution (RCE) vulnerabilities pose a significant risk to organizations. If exploited, ...

Enter the Dashboard Challenge and Watch the .conf24 Global Broadcast!

The Splunk Community Dashboard Challenge is still happening, and it's not too late to enter for the week of ...