<?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: True SSO: Bypass login page with Centrify Active Directory Integration for Splunk? in Security</title>
    <link>https://community.splunk.com/t5/Security/True-SSO-Bypass-login-page-with-Centrify-Active-Directory/m-p/33067#M1086</link>
    <description>&lt;P&gt;It should be possible, but it will require you to do a bit of work.  Splunk supports "true" single signon by being front-ended by a single-signon aware proxy server.  Splunk will implicitly allow logins in this mode using a header variable provided by the proxy server.  Centrify (according to their website) does support single-signon into Apache.  Apache can then be configured to proxy into Splunk, passing along the userid which logged in to Apache.&lt;/P&gt;

&lt;P&gt;Splunk documentation covers this at &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Admin/Usesinglesign-onwithSplunk"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Admin/Usesinglesign-onwithSplunk&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Sun, 22 Apr 2012 21:26:07 GMT</pubDate>
    <dc:creator>dwaddle</dc:creator>
    <dc:date>2012-04-22T21:26:07Z</dc:date>
    <item>
      <title>True SSO: Bypass login page with Centrify Active Directory Integration for Splunk?</title>
      <link>https://community.splunk.com/t5/Security/True-SSO-Bypass-login-page-with-Centrify-Active-Directory/m-p/33066#M1085</link>
      <description>&lt;P&gt;I'm using the Centrify Active Directory Integration for Splunk and want to know if a user's account credentials can be passed from their intranet-based workstation and logged into splunk seamlessly; that is, without being presented with a login page... like a true SSO solution.&lt;/P&gt;

&lt;P&gt;How would this be accomplished?&lt;/P&gt;</description>
      <pubDate>Sun, 22 Apr 2012 15:21:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/True-SSO-Bypass-login-page-with-Centrify-Active-Directory/m-p/33066#M1085</guid>
      <dc:creator>gryan</dc:creator>
      <dc:date>2012-04-22T15:21:20Z</dc:date>
    </item>
    <item>
      <title>Re: True SSO: Bypass login page with Centrify Active Directory Integration for Splunk?</title>
      <link>https://community.splunk.com/t5/Security/True-SSO-Bypass-login-page-with-Centrify-Active-Directory/m-p/33067#M1086</link>
      <description>&lt;P&gt;It should be possible, but it will require you to do a bit of work.  Splunk supports "true" single signon by being front-ended by a single-signon aware proxy server.  Splunk will implicitly allow logins in this mode using a header variable provided by the proxy server.  Centrify (according to their website) does support single-signon into Apache.  Apache can then be configured to proxy into Splunk, passing along the userid which logged in to Apache.&lt;/P&gt;

&lt;P&gt;Splunk documentation covers this at &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Admin/Usesinglesign-onwithSplunk"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Admin/Usesinglesign-onwithSplunk&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 22 Apr 2012 21:26:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/True-SSO-Bypass-login-page-with-Centrify-Active-Directory/m-p/33067#M1086</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2012-04-22T21:26:07Z</dc:date>
    </item>
    <item>
      <title>Re: True SSO: Bypass login page with Centrify Active Directory Integration for Splunk?</title>
      <link>https://community.splunk.com/t5/Security/True-SSO-Bypass-login-page-with-Centrify-Active-Directory/m-p/33068#M1087</link>
      <description>&lt;P&gt;Thanks for your reply. The Centrify module for Apache is not free... therefore it's not an option.&lt;/P&gt;

&lt;P&gt;I have an apache2 proxy built, however I have been unable to get it to populate the REMOTE_USER variable. Additionally, it's unclear as to what auth module is recommended for domain lookups into AD. Can you shed some light on that? &lt;/P&gt;

&lt;P&gt;I'm looking for the shortest/cheapest path toward true SSO and the Centrify addon looked like it would accomplish that, but unfortunately it only got me half way there.&lt;/P&gt;

&lt;P&gt;I do appreciate your time and your recommendations.&lt;/P&gt;

&lt;P&gt;Thanks,&lt;BR /&gt;
G&lt;/P&gt;</description>
      <pubDate>Sun, 22 Apr 2012 21:30:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/True-SSO-Bypass-login-page-with-Centrify-Active-Directory/m-p/33068#M1087</guid>
      <dc:creator>gryan</dc:creator>
      <dc:date>2012-04-22T21:30:45Z</dc:date>
    </item>
    <item>
      <title>Re: True SSO: Bypass login page with Centrify Active Directory Integration for Splunk?</title>
      <link>https://community.splunk.com/t5/Security/True-SSO-Bypass-login-page-with-Centrify-Active-Directory/m-p/33069#M1088</link>
      <description>&lt;P&gt;Thanks for your reply. The Centrify module for Apache is not free... therefore it's not an option.&lt;/P&gt;

&lt;P&gt;I have an apache2 proxy built, however I have been unable to get it to populate the REMOTE_USER variable. Additionally, it's unclear as to what auth module is recommended for domain lookups into AD. Can you shed some light on that? &lt;/P&gt;

&lt;P&gt;I'm looking for the shortest/cheapest path toward true SSO and the Centrify addon looked like it would accomplish that, but unfortunately it only got me half way there.&lt;/P&gt;

&lt;P&gt;I do appreciate your time and your recommendations.&lt;/P&gt;

&lt;P&gt;Thanks,&lt;BR /&gt;
G&lt;/P&gt;</description>
      <pubDate>Sun, 22 Apr 2012 21:31:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/True-SSO-Bypass-login-page-with-Centrify-Active-Directory/m-p/33069#M1088</guid>
      <dc:creator>gryan</dc:creator>
      <dc:date>2012-04-22T21:31:17Z</dc:date>
    </item>
    <item>
      <title>Re: True SSO: Bypass login page with Centrify Active Directory Integration for Splunk?</title>
      <link>https://community.splunk.com/t5/Security/True-SSO-Bypass-login-page-with-Centrify-Active-Directory/m-p/33070#M1089</link>
      <description>&lt;P&gt;Dwaddle is correct.  An additional bit of information is that I have tested the Centrify Apache module in a reverse proxy mode to front end other applications like SAP and Peoplesoft in addition to Splunk. It works as expected and supports WIA via Kerberos/NTLM over SPNEGO (also works with ADFS for a federated SSO).&lt;/P&gt;

&lt;P&gt;I understand gryan is not able to use the Centrify Apache module due to it not being free, but for other readers I thought this might useful information.&lt;/P&gt;

&lt;P&gt;Corey - A Centrify product manager&lt;/P&gt;</description>
      <pubDate>Sun, 22 Apr 2012 23:28:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/True-SSO-Bypass-login-page-with-Centrify-Active-Directory/m-p/33070#M1089</guid>
      <dc:creator>Corey</dc:creator>
      <dc:date>2012-04-22T23:28:32Z</dc:date>
    </item>
    <item>
      <title>Re: True SSO: Bypass login page with Centrify Active Directory Integration for Splunk?</title>
      <link>https://community.splunk.com/t5/Security/True-SSO-Bypass-login-page-with-Centrify-Active-Directory/m-p/33071#M1090</link>
      <description>&lt;P&gt;Unfortunately, you need some active code (like an Apache module) to inject that header variable.  Most single signon solutions provide such a plugin that will either (A) pick up on the existence of a valid SSO session cookie, and insert the REMOTE_USER header or (B) not seeing a valid cookie, redirect you to the SSO portal.  I know next-to-nothing about Centrify, but expect this is how their Apache module functionally works.  To avoid using it, you'll probably have to dive down into writing your own Apache modules.&lt;/P&gt;</description>
      <pubDate>Mon, 23 Apr 2012 17:40:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/True-SSO-Bypass-login-page-with-Centrify-Active-Directory/m-p/33071#M1090</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2012-04-23T17:40:50Z</dc:date>
    </item>
    <item>
      <title>Re: True SSO: Bypass login page with Centrify Active Directory Integration for Splunk?</title>
      <link>https://community.splunk.com/t5/Security/True-SSO-Bypass-login-page-with-Centrify-Active-Directory/m-p/33072#M1091</link>
      <description>&lt;P&gt;I had to do something similar to get apache to populate the REMOTE_USER variable from mod_auth_mellon. You can see what I did here, &lt;A href="http://answers.splunk.com/answers/177936/accessing-splunk-enterprise-using-adfs-authenticat.html#answer-289858" target="_blank"&gt;http://answers.splunk.com/answers/177936/accessing-splunk-enterprise-using-adfs-authenticat.html#answer-289858&lt;/A&gt; &lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 06:49:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/True-SSO-Bypass-login-page-with-Centrify-Active-Directory/m-p/33072#M1091</guid>
      <dc:creator>agitelzon</dc:creator>
      <dc:date>2020-09-29T06:49:02Z</dc:date>
    </item>
  </channel>
</rss>

