<?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 Modifying Permissions for Lookup Files viewed in the App in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Modifying-Permissions-for-Lookup-Files-viewed-in-the-App/m-p/424157#M51765</link>
    <description>&lt;P&gt;Is it possible to obfuscate lookups that users are do not have access to? I don't think it makes sense to display lookups and kv-stores that the users don't have access to edit. Also they're able to open them in the viewer which may be a bit of a security breach. &lt;/P&gt;

&lt;P&gt;We would like our users to only see what they can edit. &lt;/P&gt;</description>
    <pubDate>Thu, 24 Jan 2019 21:06:21 GMT</pubDate>
    <dc:creator>ktatis268</dc:creator>
    <dc:date>2019-01-24T21:06:21Z</dc:date>
    <item>
      <title>Modifying Permissions for Lookup Files viewed in the App</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Modifying-Permissions-for-Lookup-Files-viewed-in-the-App/m-p/424157#M51765</link>
      <description>&lt;P&gt;Is it possible to obfuscate lookups that users are do not have access to? I don't think it makes sense to display lookups and kv-stores that the users don't have access to edit. Also they're able to open them in the viewer which may be a bit of a security breach. &lt;/P&gt;

&lt;P&gt;We would like our users to only see what they can edit. &lt;/P&gt;</description>
      <pubDate>Thu, 24 Jan 2019 21:06:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Modifying-Permissions-for-Lookup-Files-viewed-in-the-App/m-p/424157#M51765</guid>
      <dc:creator>ktatis268</dc:creator>
      <dc:date>2019-01-24T21:06:21Z</dc:date>
    </item>
    <item>
      <title>Re: Modifying Permissions for Lookup Files viewed in the App</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Modifying-Permissions-for-Lookup-Files-viewed-in-the-App/m-p/424158#M51766</link>
      <description>&lt;P&gt;If you modify the permissions of the lookup and remove read access from that user's role then they will not be able to see it in the list of available lookups.&lt;/P&gt;</description>
      <pubDate>Thu, 24 Jan 2019 22:15:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Modifying-Permissions-for-Lookup-Files-viewed-in-the-App/m-p/424158#M51766</guid>
      <dc:creator>dflodstrom</dc:creator>
      <dc:date>2019-01-24T22:15:20Z</dc:date>
    </item>
    <item>
      <title>Re: Modifying Permissions for Lookup Files viewed in the App</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Modifying-Permissions-for-Lookup-Files-viewed-in-the-App/m-p/424159#M51767</link>
      <description>&lt;P&gt;That suggestion is, unfortunately, a non-stater in our environment. We have multiple SHCs all of which have over 300+ lookup files... Most of these lookups are the ones that come baked-in with other apps/TAs. &lt;/P&gt;

&lt;P&gt;There has to be a better way of obfuscating those files. The stanza below is not helping as I'd hoped. &lt;/P&gt;

&lt;P&gt;[lookups]&lt;BR /&gt;
access = read : [ ] , write : [ admin ]&lt;/P&gt;</description>
      <pubDate>Thu, 31 Jan 2019 14:47:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Modifying-Permissions-for-Lookup-Files-viewed-in-the-App/m-p/424159#M51767</guid>
      <dc:creator>ktatis268</dc:creator>
      <dc:date>2019-01-31T14:47:27Z</dc:date>
    </item>
    <item>
      <title>Re: Modifying Permissions for Lookup Files viewed in the App</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Modifying-Permissions-for-Lookup-Files-viewed-in-the-App/m-p/424160#M51768</link>
      <description>&lt;P&gt;Seeing only what you can edit is not very helpful, IMO.  Users must have read access to the lookup files needed for their dashboards and reports.  Without read access, users will see "lookup file not found" errors.&lt;BR /&gt;&lt;BR /&gt;
Only those few (typically admins) trusted to make changes to a lookup should have write access.&lt;/P&gt;</description>
      <pubDate>Thu, 31 Jan 2019 15:51:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Modifying-Permissions-for-Lookup-Files-viewed-in-the-App/m-p/424160#M51768</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2019-01-31T15:51:08Z</dc:date>
    </item>
    <item>
      <title>Re: Modifying Permissions for Lookup Files viewed in the App</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Modifying-Permissions-for-Lookup-Files-viewed-in-the-App/m-p/424161#M51769</link>
      <description>&lt;P&gt;If you only want those with write access to have read access then it shouldn't be that difficult to add this to all of the apps with lookups you want to hide. I'm not suggesting doing this one-by-one by hand but manipulating the permissions with metadata seems to be how this is done.&lt;/P&gt;</description>
      <pubDate>Thu, 31 Jan 2019 15:56:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Modifying-Permissions-for-Lookup-Files-viewed-in-the-App/m-p/424161#M51769</guid>
      <dc:creator>dflodstrom</dc:creator>
      <dc:date>2019-01-31T15:56:39Z</dc:date>
    </item>
  </channel>
</rss>

