<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: why doesn't splunk work with my reverse proxy? in Security</title>
    <link>https://community.splunk.com/t5/Security/why-doesn-t-splunk-work-with-my-reverse-proxy/m-p/46770#M1526</link>
    <description>&lt;P&gt;The reason that Splunk doesn't work with your reverse proxy is that there is a bug where using a reverse proxy w/ SSL enabled will result in redirects to login page, not a successful login(SPL-58866). This is something that has recently been discovered and there is not a fix available at the time. The issue dates back to at least 4.3.4. &lt;/P&gt;</description>
    <pubDate>Wed, 28 Nov 2012 00:03:01 GMT</pubDate>
    <dc:creator>jbsplunk</dc:creator>
    <dc:date>2012-11-28T00:03:01Z</dc:date>
    <item>
      <title>why doesn't splunk work with my reverse proxy?</title>
      <link>https://community.splunk.com/t5/Security/why-doesn-t-splunk-work-with-my-reverse-proxy/m-p/46769#M1525</link>
      <description>&lt;P&gt;my current ~/system/local/web.conf is configured as &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[settings]
httpport = 8080
mgmtHostPort = 127.0.0.1:28502
root_endpoint = /
enableSplunkWebSSL = true
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;And my apache httpd.conf &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;   &amp;lt;"Location/splunksup"&amp;gt;
    Order allow,deny 
    Allow from all 
    &amp;lt;"/Location"&amp;gt; 

    ProxyPass / &lt;A href="https://192.168.1.1:8080/" target="test_blank"&gt;https://192.168.1.1:8080/&lt;/A&gt;
    ProxyPassReverse / https:/192.168.1.1:8080/
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 28 Nov 2012 00:00:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/why-doesn-t-splunk-work-with-my-reverse-proxy/m-p/46769#M1525</guid>
      <dc:creator>Chubbybunny</dc:creator>
      <dc:date>2012-11-28T00:00:59Z</dc:date>
    </item>
    <item>
      <title>Re: why doesn't splunk work with my reverse proxy?</title>
      <link>https://community.splunk.com/t5/Security/why-doesn-t-splunk-work-with-my-reverse-proxy/m-p/46770#M1526</link>
      <description>&lt;P&gt;The reason that Splunk doesn't work with your reverse proxy is that there is a bug where using a reverse proxy w/ SSL enabled will result in redirects to login page, not a successful login(SPL-58866). This is something that has recently been discovered and there is not a fix available at the time. The issue dates back to at least 4.3.4. &lt;/P&gt;</description>
      <pubDate>Wed, 28 Nov 2012 00:03:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/why-doesn-t-splunk-work-with-my-reverse-proxy/m-p/46770#M1526</guid>
      <dc:creator>jbsplunk</dc:creator>
      <dc:date>2012-11-28T00:03:01Z</dc:date>
    </item>
    <item>
      <title>Re: why doesn't splunk work with my reverse proxy?</title>
      <link>https://community.splunk.com/t5/Security/why-doesn-t-splunk-work-with-my-reverse-proxy/m-p/46771#M1527</link>
      <description>&lt;P&gt;thanks JB!!!&lt;/P&gt;</description>
      <pubDate>Wed, 28 Nov 2012 00:04:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/why-doesn-t-splunk-work-with-my-reverse-proxy/m-p/46771#M1527</guid>
      <dc:creator>Chubbybunny</dc:creator>
      <dc:date>2012-11-28T00:04:38Z</dc:date>
    </item>
    <item>
      <title>Re: why doesn't splunk work with my reverse proxy?</title>
      <link>https://community.splunk.com/t5/Security/why-doesn-t-splunk-work-with-my-reverse-proxy/m-p/46772#M1528</link>
      <description>&lt;P&gt;Sorry to be a party-pooper...&lt;/P&gt;

&lt;P&gt;This is your scenario;&lt;/P&gt;

&lt;P&gt;User Brower &amp;lt;--Non SSL--&amp;gt; Reverse Proxy Server &amp;lt;--- SSL ---&amp;gt; Splunk&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;In httpd.conf, you need "sslproxyengine on" for this scenario&lt;/LI&gt;
&lt;LI&gt;In web.conf for 4.3.x, we introduced new attributes for web.conf. One of them will make Splunkweb more secure. But, in your scenario, this needs to disabled it.&lt;/LI&gt;
&lt;/OL&gt;

&lt;PRE&gt;
- web.conf
[settings]
httpport = 8080
mgmtHostPort = 127.0.0.1:28502
root_endpoint = /
enableSplunkWebSSL = true
# This attribute is required for a browser's insecure session 
tools.sessions.secure = False
&lt;/PRE&gt;

&lt;P&gt;For more information, please visit a spec file;&lt;BR /&gt;
&lt;PRE&gt;&lt;BR /&gt;
 - web.conf.spec&lt;BR /&gt;
 tools.sessions.secure = [True | False]&lt;BR /&gt;
    * If set to True and Splunkweb is configured to server requests using HTTPS&lt;BR /&gt;
      (see the enableSplunkWebSSL setting) then the browser will only transmit &lt;BR /&gt;
      the session cookie over HTTPS connections, increasing session security&lt;BR /&gt;
      * Defaults to True&lt;BR /&gt;
 &lt;/PRE&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Nov 2012 00:55:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/why-doesn-t-splunk-work-with-my-reverse-proxy/m-p/46772#M1528</guid>
      <dc:creator>Masa</dc:creator>
      <dc:date>2012-11-28T00:55:06Z</dc:date>
    </item>
  </channel>
</rss>

