Admin Manual

 


How Splunk Works

server.conf

This documentation does not apply to the most recent version of Splunk. Click here for the latest version.

server.conf

Server.conf controls SSL settings for your Splunk server.


To edit this configuration for your local Splunk server, make your edits in $SPLUNK_HOME/etc/bundles/local/server.conf.


You can create this file by copying examples from $SPLUNK_HOME/etc/bundles/README/server.conf.example.


Never edit files in our default bundle in $SPLUNK_HOME/etc/bundles/default or your changes may be overwritten in an upgrade.


server.conf.spec

# Copyright (C) 2005-2007 Splunk Inc.  All Rights Reserved.  Version 3.0 
#
# This file contains options for controlling the server configuration
# The only options currently available is controlling the SSL 
# configuration of the server.
#SSLConfiguration details
[sslConfig]
enableSplunkdSSL = <true|false>
        * Enables/Disables SSL on the splunkd management port.
          
enableSplunkSearchSSL = <true|false>
        * Enables/Disables SSL on the SplunkWeb.
          
keyfile = <string>
        * Server certificate file. One of these will be 
          generated by splunkd on startup, you may also 
          replace it with your own cert, PEM format, file.
        
keyfilePassword = <string>
        * Server certificate password.
caCertFile = cacert.pem
        * Public key of the signing authority.
caPath = $$SPLUNK_HOME/etc/auth
        * path where all these certs are stored.
        
certCreateScript = genSignedServerCert.sh
        * Creation script for generating certs on startup 
          of Splunk.

This documentation applies to the following versions of Splunk: 3.0 , 3.0.1 , 3.0.2 , 3.1 , 3.1.1 , 3.1.2 , 3.1.3 View the Article History for its revisions.


You must be logged into splunk.com in order to post comments. Log in now.

Was this documentation topic helpful?

If you'd like to hear back from us, please provide your email address:

We'd love to hear what you think about this topic or the documentation as a whole. Feedback you enter here will be delivered to the documentation team.

Feedback submitted, thanks!