<?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: Splunk doesn't link SSO/HTTP Header ID to Splunk ID in Security</title>
    <link>https://community.splunk.com/t5/Security/Splunk-doesn-t-link-SSO-HTTP-Header-ID-to-Splunk-ID/m-p/49612#M1625</link>
    <description>&lt;P&gt;Thank you very much.&lt;/P&gt;</description>
    <pubDate>Wed, 12 Jun 2013 19:54:33 GMT</pubDate>
    <dc:creator>lukejadamec</dc:creator>
    <dc:date>2013-06-12T19:54:33Z</dc:date>
    <item>
      <title>Splunk doesn't link SSO/HTTP Header ID to Splunk ID</title>
      <link>https://community.splunk.com/t5/Security/Splunk-doesn-t-link-SSO-HTTP-Header-ID-to-Splunk-ID/m-p/49608#M1621</link>
      <description>&lt;P&gt;I have Splunk v4.2.2 configured for SSO using an external CAS gateway with an Apache reverse proxy.&lt;/P&gt;

&lt;P&gt;I've had to set a remoteUser other than 'REMOTE_USER' to get this far, but it appears to be working/accepted to the point where Splunk isn't correlating the HTTP header remoteUser to the local splunk account. &lt;BR /&gt;
I'm getting an error:&lt;BR /&gt;
auth:56 - getSessionKey - unable to login; check credentials&lt;BR /&gt;
 decorators:192 - Could not authenticate user XXXXXXX via SSO. Does XXXXXXX have a matching splunk account with the same username?&lt;/P&gt;

&lt;P&gt;I'm able to log into the Splunk port with the same local account, but logging in via the proxy/CAS server doesn't find the same local account for the userid that's being delivered in the Remote User HTTP Header.&lt;/P&gt;

&lt;P&gt;The information in the debug/sso page all looks correct/accepted. Incoming request IP is trusted and the HTTP header/value for the remote user is correct.&lt;/P&gt;

&lt;P&gt;I have no idea how to further debug this.&lt;BR /&gt;
Is there a known fix for this, or a way to add any more details to the debug info via mrsparkle code?&lt;/P&gt;</description>
      <pubDate>Wed, 27 Jul 2011 18:27:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunk-doesn-t-link-SSO-HTTP-Header-ID-to-Splunk-ID/m-p/49608#M1621</guid>
      <dc:creator>tavandek</dc:creator>
      <dc:date>2011-07-27T18:27:40Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk doesn't link SSO/HTTP Header ID to Splunk ID</title>
      <link>https://community.splunk.com/t5/Security/Splunk-doesn-t-link-SSO-HTTP-Header-ID-to-Splunk-ID/m-p/49609#M1622</link>
      <description>&lt;P&gt;Found/fixed it.&lt;/P&gt;

&lt;P&gt;trustedIP in the server.conf file was set to the server's ip address instead of 127.0.0.1, which is apparently what splunkd requires to do SSO validation. &lt;/P&gt;

&lt;P&gt;This was separate/different from the trustedIP in the web.conf, which was being accepted.&lt;/P&gt;

&lt;P&gt;splunkd.log displayed these errors, whereas web_service.log had displayed the previous trustedIP matching errors.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Jul 2011 16:24:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunk-doesn-t-link-SSO-HTTP-Header-ID-to-Splunk-ID/m-p/49609#M1622</guid>
      <dc:creator>tavandek</dc:creator>
      <dc:date>2011-07-28T16:24:19Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk doesn't link SSO/HTTP Header ID to Splunk ID</title>
      <link>https://community.splunk.com/t5/Security/Splunk-doesn-t-link-SSO-HTTP-Header-ID-to-Splunk-ID/m-p/49610#M1623</link>
      <description>&lt;P&gt;Thank you so much, this solved a great issue I was having, you wont believe how much trouble I went through....THANK YOU!!!!!!!&lt;/P&gt;</description>
      <pubDate>Fri, 07 Dec 2012 05:05:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunk-doesn-t-link-SSO-HTTP-Header-ID-to-Splunk-ID/m-p/49610#M1623</guid>
      <dc:creator>Dark_Ichigo</dc:creator>
      <dc:date>2012-12-07T05:05:23Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk doesn't link SSO/HTTP Header ID to Splunk ID</title>
      <link>https://community.splunk.com/t5/Security/Splunk-doesn-t-link-SSO-HTTP-Header-ID-to-Splunk-ID/m-p/49611#M1624</link>
      <description>&lt;P&gt;Awesome, thanks. That was the Problem i had as well &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Feb 2013 14:06:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunk-doesn-t-link-SSO-HTTP-Header-ID-to-Splunk-ID/m-p/49611#M1624</guid>
      <dc:creator>kaddupa1</dc:creator>
      <dc:date>2013-02-11T14:06:11Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk doesn't link SSO/HTTP Header ID to Splunk ID</title>
      <link>https://community.splunk.com/t5/Security/Splunk-doesn-t-link-SSO-HTTP-Header-ID-to-Splunk-ID/m-p/49612#M1625</link>
      <description>&lt;P&gt;Thank you very much.&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jun 2013 19:54:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunk-doesn-t-link-SSO-HTTP-Header-ID-to-Splunk-ID/m-p/49612#M1625</guid>
      <dc:creator>lukejadamec</dc:creator>
      <dc:date>2013-06-12T19:54:33Z</dc:date>
    </item>
  </channel>
</rss>

