<?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: What capabilities does a REST API only user need? in Security</title>
    <link>https://community.splunk.com/t5/Security/What-capabilities-does-a-REST-API-only-user-need/m-p/656215#M17246</link>
    <description>&lt;P&gt;schedule_search is all you need from my experience&lt;/P&gt;</description>
    <pubDate>Thu, 31 Aug 2023 09:16:38 GMT</pubDate>
    <dc:creator>damode1</dc:creator>
    <dc:date>2023-08-31T09:16:38Z</dc:date>
    <item>
      <title>What capabilities does a REST API only user need?</title>
      <link>https://community.splunk.com/t5/Security/What-capabilities-does-a-REST-API-only-user-need/m-p/151458#M4613</link>
      <description>&lt;P&gt;I want to create a user that can ONLY access Splunk via the REST API and run (potentially only saved) searches. &lt;/P&gt;

&lt;P&gt;What are the minimum capabilities needed to login via REST and access saved searches? I know I need rest_properties_get but what is the bare minimum needed to login and search.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 19:00:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/What-capabilities-does-a-REST-API-only-user-need/m-p/151458#M4613</guid>
      <dc:creator>ckurtz</dc:creator>
      <dc:date>2020-09-28T19:00:31Z</dc:date>
    </item>
    <item>
      <title>Re: What capabilities does a REST API only user need?</title>
      <link>https://community.splunk.com/t5/Security/What-capabilities-does-a-REST-API-only-user-need/m-p/151459#M4614</link>
      <description>&lt;P&gt;In my environment the user role already had the following rest-related capabilities:&lt;BR /&gt;
rest_apps_view&lt;BR /&gt;
rest_properties_get&lt;BR /&gt;
rest_properties_set&lt;/P&gt;

&lt;P&gt;It turned out that this was not enough to allow a user to authenticate, I created a new role and found that just by adding a single capability the user was able to authenticate and use the API:&lt;BR /&gt;
rest_apps_management&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 07:19:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/What-capabilities-does-a-REST-API-only-user-need/m-p/151459#M4614</guid>
      <dc:creator>tmillay</dc:creator>
      <dc:date>2020-09-29T07:19:16Z</dc:date>
    </item>
    <item>
      <title>Re: What capabilities does a REST API only user need?</title>
      <link>https://community.splunk.com/t5/Security/What-capabilities-does-a-REST-API-only-user-need/m-p/151460#M4615</link>
      <description>&lt;P&gt;It does not seem possible at the moment. (Tested on 6.3.3.) A new user, with only a role with no inheritance and no capabilities, can still log into the UI of Splunk.&lt;/P&gt;

&lt;P&gt;What you can do is go through the permissions of each and every app (Apps &amp;gt; Manage Apps &amp;gt; "Permissions" on every one "visible") to disable. This won't disable logons to the UI but will render the UI effectively useless.&lt;/P&gt;

&lt;P&gt;(Keep in mind that any field extractions and knowledge objects in a visible app will then not be available for you - so keep all knowledge objects in separate, non "visible" Technology Add-ons if you want your API-only user to be able to use them!)&lt;/P&gt;</description>
      <pubDate>Fri, 08 Apr 2016 09:37:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/What-capabilities-does-a-REST-API-only-user-need/m-p/151460#M4615</guid>
      <dc:creator>Jason</dc:creator>
      <dc:date>2016-04-08T09:37:46Z</dc:date>
    </item>
    <item>
      <title>Re: What capabilities does a REST API only user need?</title>
      <link>https://community.splunk.com/t5/Security/What-capabilities-does-a-REST-API-only-user-need/m-p/151461#M4616</link>
      <description>&lt;P&gt;It took us awhile for Graphistry - &lt;CODE&gt;search&lt;/CODE&gt; and &lt;CODE&gt;rest_properties_get&lt;/CODE&gt;. You should verify, but that appears to preclude web login as desired as well.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Aug 2018 02:10:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/What-capabilities-does-a-REST-API-only-user-need/m-p/151461#M4616</guid>
      <dc:creator>leomeyerovich</dc:creator>
      <dc:date>2018-08-08T02:10:14Z</dc:date>
    </item>
    <item>
      <title>Re: What capabilities does a REST API only user need?</title>
      <link>https://community.splunk.com/t5/Security/What-capabilities-does-a-REST-API-only-user-need/m-p/631788#M16601</link>
      <description>&lt;P&gt;It's an old question, but i came though the same issue.&lt;BR /&gt;You have to enable "&lt;EM&gt;&lt;STRONG&gt;dispatch_rest_to_indexers&lt;/STRONG&gt;&lt;/EM&gt;" for the Role to query also Indexers rest api (like Storage or any other api inside Indexers side).&lt;/P&gt;</description>
      <pubDate>Wed, 22 Feb 2023 06:35:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/What-capabilities-does-a-REST-API-only-user-need/m-p/631788#M16601</guid>
      <dc:creator>verbal_666</dc:creator>
      <dc:date>2023-02-22T06:35:45Z</dc:date>
    </item>
    <item>
      <title>Re: What capabilities does a REST API only user need?</title>
      <link>https://community.splunk.com/t5/Security/What-capabilities-does-a-REST-API-only-user-need/m-p/656215#M17246</link>
      <description>&lt;P&gt;schedule_search is all you need from my experience&lt;/P&gt;</description>
      <pubDate>Thu, 31 Aug 2023 09:16:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/What-capabilities-does-a-REST-API-only-user-need/m-p/656215#M17246</guid>
      <dc:creator>damode1</dc:creator>
      <dc:date>2023-08-31T09:16:38Z</dc:date>
    </item>
  </channel>
</rss>

