<?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: Securing REST API access? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Securing-REST-API-access/m-p/66529#M13372</link>
    <description>&lt;P&gt;Is there a way to restrict access to specific endpoints only?&lt;/P&gt;</description>
    <pubDate>Thu, 10 Jan 2013 17:58:48 GMT</pubDate>
    <dc:creator>the_wolverine</dc:creator>
    <dc:date>2013-01-10T17:58:48Z</dc:date>
    <item>
      <title>Securing REST API access?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Securing-REST-API-access/m-p/66526#M13369</link>
      <description>&lt;P&gt;Any documentation or examples on how I can secure access via REST API?  Specifically, we want to restrict access to GET (no POST) and we want the standard granular access control to indexes, sources, sourcetypes, etc.&lt;/P&gt;

&lt;P&gt;I'd also like to restrict access to specific endpoints.&lt;/P&gt;

&lt;P&gt;Can this be done?&lt;/P&gt;</description>
      <pubDate>Tue, 18 Dec 2012 00:08:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Securing-REST-API-access/m-p/66526#M13369</guid>
      <dc:creator>the_wolverine</dc:creator>
      <dc:date>2012-12-18T00:08:28Z</dc:date>
    </item>
    <item>
      <title>Re: Securing REST API access?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Securing-REST-API-access/m-p/66527#M13370</link>
      <description>&lt;P&gt;Definitely it can be done. I'm not sure about what's involved in setting that up administratively, but our installation requires authentication and access to hit various endpoints.&lt;/P&gt;

&lt;P&gt;These pages describe authentication and authorization for the Splunk REST API:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.1/RESTAPI/RESTaccess"&gt;http://docs.splunk.com/Documentation/Splunk/5.0.1/RESTAPI/RESTaccess&lt;/A&gt;&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.1/RESTAPI/RESTusing#Authentication"&gt;http://docs.splunk.com/Documentation/Splunk/5.0.1/RESTAPI/RESTusing#Authentication&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Essentially, use auth/login to get the session key, and then pass the session key along in an HTTP header (Authorization request header) to get access to a given endpoint.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Dec 2012 01:23:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Securing-REST-API-access/m-p/66527#M13370</guid>
      <dc:creator>wwheeler4</dc:creator>
      <dc:date>2012-12-18T01:23:01Z</dc:date>
    </item>
    <item>
      <title>Re: Securing REST API access?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Securing-REST-API-access/m-p/66528#M13371</link>
      <description>&lt;P&gt;Have a look here :&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0/admin/authorizeconf"&gt;http://docs.splunk.com/Documentation/Splunk/5.0/admin/authorizeconf&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;There are 2 specific REST capabilitys you can assign to a role :&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[capability::rest_properties_get]
        * Required to get information from the services/properties endpoint.

[capability::rest_properties_set]
        * Required to edit the services/properties endpoint.
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;In Manager :&lt;/P&gt;

&lt;P&gt;&lt;IMG src="http://splunk-base.splunk.com//storage/Screen_Shot_2012-12-18_at_1.50.29_PM.png" alt="alt text" /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Dec 2012 06:54:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Securing-REST-API-access/m-p/66528#M13371</guid>
      <dc:creator>Damien_Dallimor</dc:creator>
      <dc:date>2012-12-18T06:54:49Z</dc:date>
    </item>
    <item>
      <title>Re: Securing REST API access?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Securing-REST-API-access/m-p/66529#M13372</link>
      <description>&lt;P&gt;Is there a way to restrict access to specific endpoints only?&lt;/P&gt;</description>
      <pubDate>Thu, 10 Jan 2013 17:58:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Securing-REST-API-access/m-p/66529#M13372</guid>
      <dc:creator>the_wolverine</dc:creator>
      <dc:date>2013-01-10T17:58:48Z</dc:date>
    </item>
    <item>
      <title>Re: Securing REST API access?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Securing-REST-API-access/m-p/66530#M13373</link>
      <description>&lt;P&gt;Are there any answers as to how to restrict access to specific endpoints?&lt;/P&gt;</description>
      <pubDate>Mon, 14 Jan 2013 18:32:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Securing-REST-API-access/m-p/66530#M13373</guid>
      <dc:creator>the_wolverine</dc:creator>
      <dc:date>2013-01-14T18:32:13Z</dc:date>
    </item>
    <item>
      <title>Re: Securing REST API access?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Securing-REST-API-access/m-p/66531#M13374</link>
      <description>&lt;P&gt;This may be useful for allowing ACCESS to specific roles, but they loose a lot of options in terms of UI access as well since they are just endpoints. &lt;/P&gt;

&lt;P&gt;Lets say we  disable the set capability, the real concern is that they still have read access. Disabling the get capability is going a little too far in my opinion. &lt;/P&gt;</description>
      <pubDate>Thu, 25 Feb 2016 18:15:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Securing-REST-API-access/m-p/66531#M13374</guid>
      <dc:creator>ben_leung</dc:creator>
      <dc:date>2016-02-25T18:15:19Z</dc:date>
    </item>
    <item>
      <title>Re: Securing REST API access?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Securing-REST-API-access/m-p/66532#M13375</link>
      <description>&lt;P&gt;I have a case open with Splunk.. Case 325092&lt;/P&gt;</description>
      <pubDate>Thu, 25 Feb 2016 18:18:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Securing-REST-API-access/m-p/66532#M13375</guid>
      <dc:creator>ben_leung</dc:creator>
      <dc:date>2016-02-25T18:18:02Z</dc:date>
    </item>
    <item>
      <title>Re: Securing REST API access?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Securing-REST-API-access/m-p/66533#M13376</link>
      <description>&lt;P&gt;Is it possible to specify the endpoints you do not want to grant visibility and then not allow access to them? &lt;/P&gt;</description>
      <pubDate>Thu, 25 Feb 2016 18:29:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Securing-REST-API-access/m-p/66533#M13376</guid>
      <dc:creator>ben_leung</dc:creator>
      <dc:date>2016-02-25T18:29:39Z</dc:date>
    </item>
    <item>
      <title>Re: Securing REST API access?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Securing-REST-API-access/m-p/66534#M13377</link>
      <description>&lt;P&gt;It took us awhile for Graphistry -- &lt;CODE&gt;search&lt;/CODE&gt; and &lt;CODE&gt;rest_properies_get&lt;/CODE&gt; (&lt;A href="https://answers.splunk.com/answers/60259/rest-api-permissions-issue.html?utm_source=answers&amp;amp;utm_medium=web&amp;amp;utm_campaign=leomeyerovich-close-social-share-678298"&gt;https://answers.splunk.com/answers/60259/rest-api-permissions-issue.html?utm_source=answers&amp;amp;utm_medium=web&amp;amp;utm_campaign=leomeyerovich-close-social-share-678298&lt;/A&gt;).&lt;/P&gt;</description>
      <pubDate>Wed, 08 Aug 2018 02:07:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Securing-REST-API-access/m-p/66534#M13377</guid>
      <dc:creator>leomeyerovich</dc:creator>
      <dc:date>2018-08-08T02:07:00Z</dc:date>
    </item>
  </channel>
</rss>

