<?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: Posting to a receiver using REST API giving  &amp;quot;insufficient permission to access this resource&amp;quot; error in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Posting-to-a-receiver-using-REST-API-giving-quot-insufficient/m-p/214454#M42189</link>
    <description>&lt;P&gt;Please see the answer posted here:&lt;/P&gt;

&lt;P&gt;&lt;A href="https://answers.splunk.com/answers/75013/minimum-permissions-required-for-using-http-simple-receiver.html"&gt;https://answers.splunk.com/answers/75013/minimum-permissions-required-for-using-http-simple-receiver.html&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Apparently there is an edit_tcp capability that needs to be defined in authorize.conf for the simple receiver to work:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.3.2/admin/Authorizeconf"&gt;http://docs.splunk.com/Documentation/Splunk/6.3.2/admin/Authorizeconf&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Fyi, the [capability::edit_tcp] stanza was already present in my system/default/authorize.conf file.  I took it out just to see if I could reproduce your problem, but I was still able to execute the REST calls.  &lt;/P&gt;</description>
    <pubDate>Wed, 06 Jan 2016 13:48:05 GMT</pubDate>
    <dc:creator>kbarker302</dc:creator>
    <dc:date>2016-01-06T13:48:05Z</dc:date>
    <item>
      <title>Posting to a receiver using REST API giving  "insufficient permission to access this resource" error</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Posting-to-a-receiver-using-REST-API-giving-quot-insufficient/m-p/214453#M42188</link>
      <description>&lt;P&gt;We are investigating how to create a Splunk log entry over the REST API via JavaScript.  I'm posting the following event via the REST API:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;curl -k -u user:password "https://tspl001:8089/services/receivers/simple?source=www&amp;amp;sourcetype=junk&amp;amp;index=angularjs_test" -d "2015-01-23 12:45:03 CST Hello there"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Here is the response:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;lt;?xml version="1.0" encoding="UTF-8"?&amp;gt;
&amp;lt;response&amp;gt;
  &amp;lt;messages&amp;gt;
    &amp;lt;msg type="WARN"&amp;gt;insufficient permission to access this resource&amp;lt;/msg&amp;gt;
  &amp;lt;/messages&amp;gt;
&amp;lt;/response&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I was told that my user has write privileges and that I'm using the correct sourcetype and index values.  I cannot file any reference to what the "www" source is.&lt;/P&gt;</description>
      <pubDate>Tue, 05 Jan 2016 21:55:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Posting-to-a-receiver-using-REST-API-giving-quot-insufficient/m-p/214453#M42188</guid>
      <dc:creator>bengwall</dc:creator>
      <dc:date>2016-01-05T21:55:43Z</dc:date>
    </item>
    <item>
      <title>Re: Posting to a receiver using REST API giving  "insufficient permission to access this resource" error</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Posting-to-a-receiver-using-REST-API-giving-quot-insufficient/m-p/214454#M42189</link>
      <description>&lt;P&gt;Please see the answer posted here:&lt;/P&gt;

&lt;P&gt;&lt;A href="https://answers.splunk.com/answers/75013/minimum-permissions-required-for-using-http-simple-receiver.html"&gt;https://answers.splunk.com/answers/75013/minimum-permissions-required-for-using-http-simple-receiver.html&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Apparently there is an edit_tcp capability that needs to be defined in authorize.conf for the simple receiver to work:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.3.2/admin/Authorizeconf"&gt;http://docs.splunk.com/Documentation/Splunk/6.3.2/admin/Authorizeconf&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Fyi, the [capability::edit_tcp] stanza was already present in my system/default/authorize.conf file.  I took it out just to see if I could reproduce your problem, but I was still able to execute the REST calls.  &lt;/P&gt;</description>
      <pubDate>Wed, 06 Jan 2016 13:48:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Posting-to-a-receiver-using-REST-API-giving-quot-insufficient/m-p/214454#M42189</guid>
      <dc:creator>kbarker302</dc:creator>
      <dc:date>2016-01-06T13:48:05Z</dc:date>
    </item>
    <item>
      <title>Re: Posting to a receiver using REST API giving  "insufficient permission to access this resource" error</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Posting-to-a-receiver-using-REST-API-giving-quot-insufficient/m-p/214455#M42190</link>
      <description>&lt;P&gt;Assigning the edit_tcp attribute solved the issue. Thanks.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Jan 2016 17:29:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Posting-to-a-receiver-using-REST-API-giving-quot-insufficient/m-p/214455#M42190</guid>
      <dc:creator>bengwall</dc:creator>
      <dc:date>2016-01-06T17:29:51Z</dc:date>
    </item>
  </channel>
</rss>

