Splunk® Enterprise

Securing the Splunk Platform

Acrobat logo Download manual as PDF


Acrobat logo Download topic as PDF

Turn on HTTPS encryption for Splunk Web using the web.conf configuration file

You can enable HTTPS communication between your browser and Splunk Web by using the web.conf configuration file.

The form of encryption that this procedure describes does not meet standards for security if you use the default certificates that come with the product. To ensure communications are completely secure, you must exchange the default certificates for your own and configure secure authentication. See Secure Splunk Web with your own certificate for information about replacing the default certificates.

If the web.conf file is not already present in your Splunk Enterprise configuration directory in $SPLUNK_HOME/etc/system/local, you can create the file there, or in a custom application directory in the $SPLUNK_HOME/etc/apps/ file. For information on configuration files in general, see About configuration files.

  1. Open the web.conf configuration file for editing.
  2. In the file, within the [settings] stanza, configure the enableSplunkWebSSL setting to true:
    [settings]
    httpport = <https port number>
    enableSplunkWebSSL = true
    

    Unless you configure Splunk Enterprise to use your own certificates, it uses the default certificates when you turn on encryption.

  3. Restart Splunk Enterprise. See Restart Splunk in the Admin Manual for instructions.
  4. After Splunk Enterprise restarts, to access Splunk Web on that instance, use "https://<your site name>:<port>" for the URL.
Last modified on 10 November, 2021
PREVIOUS
Turn on HTTPS encryption for Splunk Web with Splunk Web
  NEXT
Secure Splunk Web with your own certificate

This documentation applies to the following versions of Splunk® Enterprise: 6.3.0, 6.3.1, 6.3.2, 6.3.3, 6.3.4, 6.3.5, 6.3.6, 6.3.7, 6.3.8, 6.3.9, 6.3.10, 6.3.11, 6.3.12, 6.3.13, 6.3.14, 6.4.0, 6.4.1, 6.4.2, 6.4.3, 6.4.4, 6.4.5, 6.4.6, 6.4.7, 6.4.8, 6.4.9, 6.4.10, 6.4.11, 6.5.0, 6.5.1, 6.5.2, 6.5.3, 6.5.4, 6.5.5, 6.5.6, 6.5.7, 6.5.8, 6.5.9, 6.5.10, 6.6.0, 6.6.1, 6.6.2, 6.6.3, 6.6.4, 6.6.5, 6.6.6, 6.6.7, 6.6.8, 6.6.9, 6.6.10, 6.6.11, 6.6.12, 7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.0.7, 7.0.8, 7.0.9, 7.0.10, 7.0.11, 7.0.13, 7.1.0, 7.1.1, 7.1.2, 7.1.3, 7.1.4, 7.1.5, 7.1.6, 7.1.7, 7.1.8, 7.1.9, 7.1.10, 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6, 7.2.7, 7.2.8, 7.2.9, 7.2.10, 7.3.0, 7.3.1, 7.3.2, 7.3.3, 7.3.4, 7.3.5, 7.3.6, 7.3.7, 7.3.8, 7.3.9, 8.0.0, 8.0.1, 8.0.2, 8.0.3, 8.0.4, 8.0.5, 8.0.6, 8.0.7, 8.0.8, 8.0.9, 8.0.10, 8.1.0, 8.1.1, 8.1.2, 8.1.3, 8.1.4, 8.1.5, 8.1.6, 8.1.7, 8.2.0, 8.2.1, 8.2.2, 8.2.3


Was this documentation topic helpful?

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

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters