<?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: ess_admin role issues in Splunk Enterprise Security</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/ess-admin-role-issues/m-p/418457#M5121</link>
    <description>&lt;P&gt;We are running ES with the ess_admin user only, And it works!.&lt;/P&gt;

&lt;P&gt;BUT you need to be sure there are no references to admin in de default.meta.&lt;BR /&gt;&lt;BR /&gt;
Some config is "owned by admin"  and it will fail is tou don't remove is.&lt;BR /&gt;
We run this to be sure admin is removed:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;find . -type f -name default.meta -exec sed -i 's/owner = admin/#owner = admin/g' {} +
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;and&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;find . -name *.meta -type f -print | xargs sed -i '/^access/c\access = read : [ * ], write : [ ess_admin ]'
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Thu, 18 Apr 2019 11:27:54 GMT</pubDate>
    <dc:creator>teunlaan</dc:creator>
    <dc:date>2019-04-18T11:27:54Z</dc:date>
    <item>
      <title>ess_admin role issues</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/ess-admin-role-issues/m-p/418455#M5119</link>
      <description>&lt;P&gt;Hello, &lt;BR /&gt;
I have a splunk cloud managed deployment which has ES installed on it. &lt;/P&gt;

&lt;P&gt;First thing is that my user has only ess_admin role without any other Splunk platform admin role, which according to Splunk docs is necessary for ess_admin role. &lt;BR /&gt;
(&lt;A href="https://docs.splunk.com/Documentation/ES/5.2.2/Install/ConfigureUsersRoles" target="_blank"&gt;https://docs.splunk.com/Documentation/ES/5.2.2/Install/ConfigureUsersRoles&lt;/A&gt;). &lt;BR /&gt;
Is it really a demand for this role ? I have all the needed ES permissions working just fine at the moment. &lt;/P&gt;

&lt;P&gt;Second is that i ran the command  &lt;CODE&gt;| rest /services/authorization/roles&lt;/CODE&gt; and i can see that ess_admin role has access to _internal and _* in the "srchIndexDefault", but for some weird reason i don't really have permissions for those kind of indexes and i can't figure out why.&lt;/P&gt;

&lt;P&gt;Thanks for any help!!&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 00:11:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/ess-admin-role-issues/m-p/418455#M5119</guid>
      <dc:creator>astatrial</dc:creator>
      <dc:date>2020-09-30T00:11:14Z</dc:date>
    </item>
    <item>
      <title>Re: ess_admin role issues</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/ess-admin-role-issues/m-p/418456#M5120</link>
      <description>&lt;P&gt;I think i figured out why it acts like this. &lt;/P&gt;

&lt;P&gt;In the srchIndexesAllowed there is nothing, so although that in the srchIndexesDefault there are all the indexes, it doesn't use them.&lt;/P&gt;

&lt;P&gt;On the other hand in the srchIndexesAllowed of the user role, there is * which represent according to authorize.conf all the non-internal indexes. So when there is * in ess_admin role  Imported_srchIndexesAllowed, it refers to all the non internal indexes. &lt;/P&gt;

&lt;P&gt;Still i don't understand if Splunk platform admin role is necessary for ess_admin role...&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 00:11:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/ess-admin-role-issues/m-p/418456#M5120</guid>
      <dc:creator>astatrial</dc:creator>
      <dc:date>2020-09-30T00:11:16Z</dc:date>
    </item>
    <item>
      <title>Re: ess_admin role issues</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise-Security/ess-admin-role-issues/m-p/418457#M5121</link>
      <description>&lt;P&gt;We are running ES with the ess_admin user only, And it works!.&lt;/P&gt;

&lt;P&gt;BUT you need to be sure there are no references to admin in de default.meta.&lt;BR /&gt;&lt;BR /&gt;
Some config is "owned by admin"  and it will fail is tou don't remove is.&lt;BR /&gt;
We run this to be sure admin is removed:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;find . -type f -name default.meta -exec sed -i 's/owner = admin/#owner = admin/g' {} +
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;and&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;find . -name *.meta -type f -print | xargs sed -i '/^access/c\access = read : [ * ], write : [ ess_admin ]'
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 18 Apr 2019 11:27:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise-Security/ess-admin-role-issues/m-p/418457#M5121</guid>
      <dc:creator>teunlaan</dc:creator>
      <dc:date>2019-04-18T11:27:54Z</dc:date>
    </item>
  </channel>
</rss>

