<?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 Is there a way to use default.meta to lock down write access to field extractions? in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Is-there-a-way-to-use-default-meta-to-lock-down-write-access-to/m-p/309345#M92786</link>
    <description>&lt;P&gt;We are considering locking down access to share field extractions.   Is anyone aware of a way to do this easily?   We want users to share other KOs so we don't want to completely remove write access to the search app.&lt;/P&gt;</description>
    <pubDate>Tue, 23 May 2017 23:40:42 GMT</pubDate>
    <dc:creator>the_wolverine</dc:creator>
    <dc:date>2017-05-23T23:40:42Z</dc:date>
    <item>
      <title>Is there a way to use default.meta to lock down write access to field extractions?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Is-there-a-way-to-use-default-meta-to-lock-down-write-access-to/m-p/309345#M92786</link>
      <description>&lt;P&gt;We are considering locking down access to share field extractions.   Is anyone aware of a way to do this easily?   We want users to share other KOs so we don't want to completely remove write access to the search app.&lt;/P&gt;</description>
      <pubDate>Tue, 23 May 2017 23:40:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Is-there-a-way-to-use-default-meta-to-lock-down-write-access-to/m-p/309345#M92786</guid>
      <dc:creator>the_wolverine</dc:creator>
      <dc:date>2017-05-23T23:40:42Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a way to use default.meta to lock down write access to field extractions?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Is-there-a-way-to-use-default-meta-to-lock-down-write-access-to/m-p/309346#M92787</link>
      <description>&lt;P&gt;You need something like this in your local.meta in the search app:&lt;/P&gt;

&lt;P&gt;[props]&lt;BR /&gt;
access = read : [ admin ], write : [ admin ]&lt;BR /&gt;
export = none&lt;/P&gt;

&lt;P&gt;Locking it down to admin only and then from there allow which ever roles.&lt;BR /&gt;
Also make sure the roles have capability to write in the search app first or this won't work.&lt;/P&gt;</description>
      <pubDate>Wed, 24 May 2017 05:45:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Is-there-a-way-to-use-default-meta-to-lock-down-write-access-to/m-p/309346#M92787</guid>
      <dc:creator>ben_leung</dc:creator>
      <dc:date>2017-05-24T05:45:33Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a way to use default.meta to lock down write access to field extractions?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Is-there-a-way-to-use-default-meta-to-lock-down-write-access-to/m-p/309347#M92788</link>
      <description>&lt;P&gt;Thanks &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; It worked.  To be clear this doesn't prevent the field extraction from being created.  Users can still create their own private extractions, they just will not be able to share them.&lt;/P&gt;

&lt;P&gt;[props]&lt;BR /&gt;
export = system&lt;BR /&gt;
access = read : [ * ], write : [ admin ]&lt;/P&gt;

&lt;P&gt;[transforms]&lt;BR /&gt;
export = system&lt;BR /&gt;
access = read : [ * ], write : [ admin ]&lt;/P&gt;</description>
      <pubDate>Wed, 31 May 2017 17:19:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Is-there-a-way-to-use-default-meta-to-lock-down-write-access-to/m-p/309347#M92788</guid>
      <dc:creator>the_wolverine</dc:creator>
      <dc:date>2017-05-31T17:19:59Z</dc:date>
    </item>
  </channel>
</rss>

