<?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: pass through authentication to custom command in Security</title>
    <link>https://community.splunk.com/t5/Security/pass-through-authentication-to-custom-command/m-p/197274#M5773</link>
    <description>&lt;P&gt;Just found another answer which could be helpful:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://answers.splunk.com/answers/23504/determine-currently-logged-in-username"&gt;http://answers.splunk.com/answers/23504/determine-currently-logged-in-username&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 17 Jun 2014 12:17:19 GMT</pubDate>
    <dc:creator>MuS</dc:creator>
    <dc:date>2014-06-17T12:17:19Z</dc:date>
    <item>
      <title>pass through authentication to custom command</title>
      <link>https://community.splunk.com/t5/Security/pass-through-authentication-to-custom-command/m-p/197272#M5771</link>
      <description>&lt;P&gt;how can one pass through the credentials of the currently logged in user to a back end.&lt;BR /&gt;
example: use a connector to a directory and bind using the dn and password of the logged in user (we authenticate and authorize to the same directory but not using kerberos as it is not an AD)&lt;BR /&gt;
another example: use a connector to jira and user username and password to log into jira&lt;BR /&gt;
essentially ensuring that the user does not see more in the target system then when logged in directly. Often it makes sense to see more and hide behind reports and forms but often it would be more straightforward to pass through authentication.&lt;/P&gt;

&lt;P&gt;Is there a way to do this? Use the current users credentials?&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jan 2014 10:27:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/pass-through-authentication-to-custom-command/m-p/197272#M5771</guid>
      <dc:creator>dominiquevocat</dc:creator>
      <dc:date>2014-01-07T10:27:14Z</dc:date>
    </item>
    <item>
      <title>Re: pass through authentication to custom command</title>
      <link>https://community.splunk.com/t5/Security/pass-through-authentication-to-custom-command/m-p/197273#M5772</link>
      <description>&lt;P&gt;Hi dominiquevocat,&lt;/P&gt;

&lt;P&gt;you should have a look at this blog post &lt;A href="http://www.georgestarcher.com/splunk-alert-scripts-automating-control/"&gt;http://www.georgestarcher.com/splunk-alert-scripts-automating-control/&lt;/A&gt;, in Step 10 @starcher is using a this:&lt;/P&gt;

&lt;BLOCKQUOTE&gt;
&lt;P&gt;&lt;EM&gt;Our alert script inherits the path to the search results from the arguments,&lt;BR /&gt;
and it uses the session ID which is keyed to the alert script user account&lt;BR /&gt;
to make a REST API call back into Splunk to request the saved&lt;BR /&gt;
credentials we want via my Python class&lt;/EM&gt;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;

&lt;P&gt;maybe you could use this as example and adapt it to your needs?&lt;/P&gt;

&lt;P&gt;cheers, MuS &lt;/P&gt;</description>
      <pubDate>Mon, 16 Jun 2014 08:47:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/pass-through-authentication-to-custom-command/m-p/197273#M5772</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2014-06-16T08:47:39Z</dc:date>
    </item>
    <item>
      <title>Re: pass through authentication to custom command</title>
      <link>https://community.splunk.com/t5/Security/pass-through-authentication-to-custom-command/m-p/197274#M5773</link>
      <description>&lt;P&gt;Just found another answer which could be helpful:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://answers.splunk.com/answers/23504/determine-currently-logged-in-username"&gt;http://answers.splunk.com/answers/23504/determine-currently-logged-in-username&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Jun 2014 12:17:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/pass-through-authentication-to-custom-command/m-p/197274#M5773</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2014-06-17T12:17:19Z</dc:date>
    </item>
  </channel>
</rss>

