While there is ample documentation on certificate generation and application to both Splunk Web, Indexers, and Forwarders-- we often find that securing post-default deployment scenarios during PS engagements are no fun. We haven't had good luck with just 'pushing' certificates and having Universal Forwarders properly utilize them (at least in Windows environments). Utilizing the Deployment Server and pushing your own app and config packages still have clear text in many scenarios.
We would like to see a feature added for complete Web GUI of Splunk Certificate Management including:
Components: universal forwarders, indexers, and Splunk web server
Action/abilities for administrator user from within WebUI:
Import and use 3rd party signed CA certificates, and their respective keys (including mutual authentication client certs required)
Automated abilities Generate, replace/renew, and deploy certificates to all connecting forwarders (Windows and Linux)
Warning messages when certificates will expire
Enable a 'quick start' deployment default options of either using 3rd party signed certs or using self signed certs during installation for secure NOT JUST universal forwarder agent check in/control status messages but the actual data being forwarded from them. This also includes automatic proper TLS use ready for receiver
... View more
Hello I get an error when attempting to utilize a self-signed Splunk cert generated from the splunk openssl through the tutorial found here
When after generating the keys I put them in the program files folder under \etc\auth and then my outputs.conf is set appropriately. The forwarder continues to send in clear text and the following error is within splunkd. "ERROR SSLCommon - Can't read key file C:\Program Files\SplunkUniversalForwarder\etc\auth\foocert.pem errno=151441516 error:0906D06C:PEM routines:PEM_read_bio:no start line."
I've investigated the pem file and compared it to others. Since it was windows I looked at them cert in both notepad++ and notepad regular and made adjusted line breaks accordingly even without word wrap as an attempt to resolve. I ensured the top of the file included "-----BEGIN CERTIFICATE-----" exactly 5 dashes each with no extra spacing. as well as the footer "-----END CERTIFICATE-----" the key looks like your average normal key. When examining the file with all non-printables notepad++ reports "CR LF" byte codes at each line. The other PEM files seem to have them too; which I suspect should be fine. I would like to use the same certificate pair made for the indexer as the UF; but the I do not have the private key right after the public key in the same pem file. I doubt that would generate the error but then again I'm unsure. Does the 'splunk open ssl' command use in Windows generate a file that needs to be tweaked before utilization? If so please advise.
... View more