<?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: Insecure login issue in new splunk setup in Security</title>
    <link>https://community.splunk.com/t5/Security/Insecure-login-issue-in-new-splunk-setup/m-p/83402#M14124</link>
    <description>&lt;P&gt;Our web.conf has enable_insecure_login set to true.&lt;/P&gt;</description>
    <pubDate>Mon, 28 Sep 2020 14:54:04 GMT</pubDate>
    <dc:creator>strive</dc:creator>
    <dc:date>2020-09-28T14:54:04Z</dc:date>
    <item>
      <title>Insecure login issue in new splunk setup</title>
      <link>https://community.splunk.com/t5/Security/Insecure-login-issue-in-new-splunk-setup/m-p/83401#M14123</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;In our system, we are always getting insecure login error. Our system is on RHEL 5.x. When I reboot the Search Head node, the 8000 port will be assigned and SH starts normally. Now when I try to login to the system, I get insecure login pop-up message in Firefox and IE. When i check the SH and try to stop and restart splunk on SH node, i get message 8000 port is not available.&lt;/P&gt;

&lt;P&gt;Is there any settings that should be enabled on SH node to avoid the insecure login issue.&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;

&lt;P&gt;Strive&lt;/P&gt;</description>
      <pubDate>Fri, 04 Oct 2013 19:05:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Insecure-login-issue-in-new-splunk-setup/m-p/83401#M14123</guid>
      <dc:creator>strive</dc:creator>
      <dc:date>2013-10-04T19:05:07Z</dc:date>
    </item>
    <item>
      <title>Re: Insecure login issue in new splunk setup</title>
      <link>https://community.splunk.com/t5/Security/Insecure-login-issue-in-new-splunk-setup/m-p/83402#M14124</link>
      <description>&lt;P&gt;Our web.conf has enable_insecure_login set to true.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 14:54:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Insecure-login-issue-in-new-splunk-setup/m-p/83402#M14124</guid>
      <dc:creator>strive</dc:creator>
      <dc:date>2020-09-28T14:54:04Z</dc:date>
    </item>
    <item>
      <title>Re: Insecure login issue in new splunk setup</title>
      <link>https://community.splunk.com/t5/Security/Insecure-login-issue-in-new-splunk-setup/m-p/83403#M14125</link>
      <description>&lt;P&gt;enable_insecure_login is a setting that was added to allow a dashboard to be rendered in something other than Splunk.  Are you doing that in your enviormnent?  If not you probably want to disable the setting since it allows credentials to be passed in the clear (hence calling it insecure login).  With that said I do not believe that setting is related to your setting.  What version of Splunk are you running?  Do you have update checking turned on?  If you inspect the page in Firebug (or something similar) to do you see an insecure elements in the HTML?&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 14:54:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Insecure-login-issue-in-new-splunk-setup/m-p/83403#M14125</guid>
      <dc:creator>matt</dc:creator>
      <dc:date>2020-09-28T14:54:09Z</dc:date>
    </item>
  </channel>
</rss>

