<?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: Curl with negotiate to run a search in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Curl-with-negotiate-to-run-a-search/m-p/168695#M34151</link>
    <description>&lt;P&gt;To be clear...my fail above was trying to access REST API endpoints not available through the web UI. &lt;/P&gt;

&lt;P&gt;Not supporting SSO for the REST API seems like a miss to me.  Would love to hear peoples thoughts if there are good security reasons for not having it.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.0.1/Security/HowSplunkSSOworks"&gt;http://docs.splunk.com/Documentation/Splunk/6.0.1/Security/HowSplunkSSOworks&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;"Splunk's SSO implementation supports logging into Splunk via Splunk Web only. Since Splunk SSO relies on cookies to save authentication information, SSO cannot be used for CLI authentication to Splunk. Invoking &lt;A href="https://localhost:8089"&gt;https://localhost:8089&lt;/A&gt; (or the assigned management port) still requires independent authentication."&lt;/P&gt;</description>
    <pubDate>Thu, 27 Feb 2014 23:28:39 GMT</pubDate>
    <dc:creator>juniormint</dc:creator>
    <dc:date>2014-02-27T23:28:39Z</dc:date>
    <item>
      <title>Curl with negotiate to run a search</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Curl-with-negotiate-to-run-a-search/m-p/168694#M34150</link>
      <description>&lt;P&gt;I am interacting with a splunk server using apache to do single sign to the Splunk web UI.  &lt;/P&gt;

&lt;P&gt;If I go to the following url in a web browser I get signed on and the page loads; which is great. &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&lt;A href="https://mysplunk.test.com/en-US/app/MyApp/MyDashboard" target="test_blank"&gt;https://mysplunk.test.com/en-US/app/MyApp/MyDashboard&lt;/A&gt; 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Using curl I can run something like the following and get my dashboard back; which seems great as well.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;curl --negotiate --user a:a &lt;A href="https://mysplunk.test.com/en-US/app/MyApp/MyDashboard" target="test_blank"&gt;https://mysplunk.test.com/en-US/app/MyApp/MyDashboard&lt;/A&gt; 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I was hoping that the following would also work...but no.  Do I just have a simple error, or is this not possible?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;curl --negotiate -u a:a &lt;A href="https://mysplunk.test.com/servicesNS/admin/search/search/jobs/export" target="test_blank"&gt;https://mysplunk.test.com/servicesNS/admin/search/search/jobs/export&lt;/A&gt; -d output_mode=json --data-urlencode search="| eventcount summarize=f index=MyApps_* | stats count by index"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The response I get is &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;This resource can be found at &amp;lt;a href='https://localhost:8443/en-US/servicesNS/admin/search/search/jobs/export'&amp;gt;https://localhost:8443/en-US/servicesNS/admin/search/search/jobs/export&amp;lt;/a&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 27 Feb 2014 17:23:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Curl-with-negotiate-to-run-a-search/m-p/168694#M34150</guid>
      <dc:creator>juniormint</dc:creator>
      <dc:date>2014-02-27T17:23:17Z</dc:date>
    </item>
    <item>
      <title>Re: Curl with negotiate to run a search</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Curl-with-negotiate-to-run-a-search/m-p/168695#M34151</link>
      <description>&lt;P&gt;To be clear...my fail above was trying to access REST API endpoints not available through the web UI. &lt;/P&gt;

&lt;P&gt;Not supporting SSO for the REST API seems like a miss to me.  Would love to hear peoples thoughts if there are good security reasons for not having it.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.0.1/Security/HowSplunkSSOworks"&gt;http://docs.splunk.com/Documentation/Splunk/6.0.1/Security/HowSplunkSSOworks&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;"Splunk's SSO implementation supports logging into Splunk via Splunk Web only. Since Splunk SSO relies on cookies to save authentication information, SSO cannot be used for CLI authentication to Splunk. Invoking &lt;A href="https://localhost:8089"&gt;https://localhost:8089&lt;/A&gt; (or the assigned management port) still requires independent authentication."&lt;/P&gt;</description>
      <pubDate>Thu, 27 Feb 2014 23:28:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Curl-with-negotiate-to-run-a-search/m-p/168695#M34151</guid>
      <dc:creator>juniormint</dc:creator>
      <dc:date>2014-02-27T23:28:39Z</dc:date>
    </item>
  </channel>
</rss>

