<?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: Splunk App for VMware: What capabilities are needed for the Data Collection Node user (collection configuration) to perform scheduling tasks? in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-App-for-VMware-What-capabilities-are-needed-for-the-Data/m-p/200722#M21005</link>
    <description>&lt;P&gt;Hi. &lt;/P&gt;

&lt;P&gt;As far as I have experienced you need a user/role with "admin_all_objects" capabilities to push collection jobs on the DCN. I tried several different combination of capabilities, but it always results in the "admin_all_objects" capability. &lt;/P&gt;

&lt;P&gt;You could create a role with only "admin_all_objects" capability, but without access to any index. In case of a misuse the account can't give himself additional rights or access to any index. The downside of this solution is that he's able to edit/delete/create knowledge objects. &lt;/P&gt;

&lt;P&gt;Best Regards¨&lt;BR /&gt;
Markus&lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2020 09:54:54 GMT</pubDate>
    <dc:creator>markusspitzli2</dc:creator>
    <dc:date>2020-09-29T09:54:54Z</dc:date>
    <item>
      <title>Splunk App for VMware: What capabilities are needed for the Data Collection Node user (collection configuration) to perform scheduling tasks?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-App-for-VMware-What-capabilities-are-needed-for-the-Data/m-p/200721#M21004</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;When configuring the Data Collection Nodes (DCN) in the collection configuration for the Splunk App for VMware, a "Splunk Forwarder Username" has to be provided. This user is used by the Scheduler to push the collection jobs to the DCNs. &lt;BR /&gt;
By default, the admin user is used.&lt;/P&gt;

&lt;P&gt;Does anyone know precisely what capabilities that forwarder user needs to perform the scheduling tasks?&lt;/P&gt;

&lt;P&gt;I want to delegate the collection configuration setup to the VMWare Admins, but do not want to give them the admin password. So, I want to set up a dedicated user and role for the DCN scheduler with only the capabilities needed.&lt;/P&gt;

&lt;P&gt;Thanks &amp;amp; regards&lt;BR /&gt;
flle&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jun 2016 11:59:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-App-for-VMware-What-capabilities-are-needed-for-the-Data/m-p/200721#M21004</guid>
      <dc:creator>flle</dc:creator>
      <dc:date>2016-06-08T11:59:34Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk App for VMware: What capabilities are needed for the Data Collection Node user (collection configuration) to perform scheduling tasks?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-App-for-VMware-What-capabilities-are-needed-for-the-Data/m-p/200722#M21005</link>
      <description>&lt;P&gt;Hi. &lt;/P&gt;

&lt;P&gt;As far as I have experienced you need a user/role with "admin_all_objects" capabilities to push collection jobs on the DCN. I tried several different combination of capabilities, but it always results in the "admin_all_objects" capability. &lt;/P&gt;

&lt;P&gt;You could create a role with only "admin_all_objects" capability, but without access to any index. In case of a misuse the account can't give himself additional rights or access to any index. The downside of this solution is that he's able to edit/delete/create knowledge objects. &lt;/P&gt;

&lt;P&gt;Best Regards¨&lt;BR /&gt;
Markus&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 09:54:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-App-for-VMware-What-capabilities-are-needed-for-the-Data/m-p/200722#M21005</guid>
      <dc:creator>markusspitzli2</dc:creator>
      <dc:date>2020-09-29T09:54:54Z</dc:date>
    </item>
  </channel>
</rss>

