<?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 Unable to assign permissions to a Field Extraction for all Splunk Users in Security</title>
    <link>https://community.splunk.com/t5/Security/Unable-to-assign-permissions-to-a-Field-Extraction-for-all/m-p/315236#M8234</link>
    <description>&lt;P&gt;Hi All,&lt;/P&gt;

&lt;P&gt;I receive the following error when assigning full permissions to field extractions that I created in splunk.&lt;/P&gt;

&lt;P&gt;Splunk could not update permissions for resource data/props/extractions [HTTP 500] Splunkd internal error; [{'text': "\n In handler 'props-extract': Data could not be written: /nobody/search/props/netscreen:firewall/EXTRACT-user: by\s(?[^\/]+)", 'code': None, 'type': 'ERROR'}]&lt;/P&gt;

&lt;P&gt;Please advise.&lt;/P&gt;</description>
    <pubDate>Sat, 13 Jan 2018 00:40:09 GMT</pubDate>
    <dc:creator>zzaveri</dc:creator>
    <dc:date>2018-01-13T00:40:09Z</dc:date>
    <item>
      <title>Unable to assign permissions to a Field Extraction for all Splunk Users</title>
      <link>https://community.splunk.com/t5/Security/Unable-to-assign-permissions-to-a-Field-Extraction-for-all/m-p/315236#M8234</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;

&lt;P&gt;I receive the following error when assigning full permissions to field extractions that I created in splunk.&lt;/P&gt;

&lt;P&gt;Splunk could not update permissions for resource data/props/extractions [HTTP 500] Splunkd internal error; [{'text': "\n In handler 'props-extract': Data could not be written: /nobody/search/props/netscreen:firewall/EXTRACT-user: by\s(?[^\/]+)", 'code': None, 'type': 'ERROR'}]&lt;/P&gt;

&lt;P&gt;Please advise.&lt;/P&gt;</description>
      <pubDate>Sat, 13 Jan 2018 00:40:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Unable-to-assign-permissions-to-a-Field-Extraction-for-all/m-p/315236#M8234</guid>
      <dc:creator>zzaveri</dc:creator>
      <dc:date>2018-01-13T00:40:09Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to assign permissions to a Field Extraction for all Splunk Users</title>
      <link>https://community.splunk.com/t5/Security/Unable-to-assign-permissions-to-a-Field-Extraction-for-all/m-p/315237#M8235</link>
      <description>&lt;P&gt;hey&lt;BR /&gt;
One of the user faced same problem and he followed following steps to solve this issue&lt;/P&gt;

&lt;P&gt;1) You probably copied the file as user &lt;CODE&gt;root&lt;/CODE&gt; but Splunk is running as a lesser-priviliged user (e.g. &lt;CODE&gt;splunk&lt;/CODE&gt;) which does not have permission to write to the file. You nee to do a &lt;CODE&gt;chown&lt;/CODE&gt; to match the user running splunk or &lt;CODE&gt;chmod&lt;/CODE&gt; to allow others to write to the file.&lt;BR /&gt;
2) gave full control of $Splunk_home to the Everyone user group. (Shotgun approach)&lt;BR /&gt;
3) On the web interface, on the save screen for the field extraction, he clicked the All Apps button on the Permissions row, (&lt;CODE&gt;Owner&lt;/CODE&gt; had been selected by default).  This showed a table of users with columns for name, read permissions, and write permissions. There was a line for the user group Everyone, I checked the Write Permissions box, and I was able to save.&lt;/P&gt;

&lt;P&gt;let me know if this helps you!&lt;/P&gt;</description>
      <pubDate>Sat, 13 Jan 2018 05:22:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Unable-to-assign-permissions-to-a-Field-Extraction-for-all/m-p/315237#M8235</guid>
      <dc:creator>mayurr98</dc:creator>
      <dc:date>2018-01-13T05:22:07Z</dc:date>
    </item>
  </channel>
</rss>

