<?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: User Roles and How to restrict server access from user group in New SAS User</title>
    <link>https://communities.sas.com/t5/New-SAS-User/User-Roles-and-How-to-restrict-server-access-from-user-group/m-p/512883#M2465</link>
    <description>&lt;P&gt;If you want to prevent users from writing to/reading from a specific location on the server, you either have to restrict them from using the relevant code elements (impractical, as these are needed for eg import/export tasks), or you have to make sure that those locations are made secure on the operating system level.&lt;/P&gt;
&lt;P&gt;Library permissions can be handled in SAS metadata, but in order to make them "stick" you need to define those libraries as "metadata bound". Otherwise executing a simple libname can always undercut the metadata, unless you also restrict permissions on the OS level (see above).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;My preferred path is to use the proper permissions in the operating system. If a user does not have read/execute permissions on the directory of a library, a libname for that directory will fail, and the library will not appear in the server list.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Note that relying on third-party tools (SAS in this case) to keep your operating system safe is foolish at best. Use the tools provided by the system itself (see Maxims 14 &amp;amp; 15).&lt;/P&gt;</description>
    <pubDate>Wed, 14 Nov 2018 09:55:00 GMT</pubDate>
    <dc:creator>Kurt_Bremser</dc:creator>
    <dc:date>2018-11-14T09:55:00Z</dc:date>
    <item>
      <title>User Roles and How to restrict server access from user group</title>
      <link>https://communities.sas.com/t5/New-SAS-User/User-Roles-and-How-to-restrict-server-access-from-user-group/m-p/512866#M2454</link>
      <description>&lt;P&gt;Hello SAS community,&amp;nbsp;&lt;BR /&gt;My objective is to restrict access for a group of users - using SAS Enterprise Guide and Management Console. So i have gotten this far and just realized that the user can actually just click on the server tab and the user has permissions and access to files on the server...&lt;BR /&gt;&lt;BR /&gt;How i restricted the user group:&lt;BR /&gt;[1] In management console&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;i created a user group and then added user/members to the group.&amp;nbsp;&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;then i clicked on to the folders tab and added the newly created user group in all folders paths, libraries and datasets that i do not want the group to access - hence i add the group to the user group list and deny all permissions.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;[2] The result is what i want and inside Enterprise Guide i see that the restricted user group will not even see the directory/paths, libraries and datasets restricted.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;The only issue i have now is that the user is still able to access the Servers and has permission to write and update any files on the server... I tried adding the group on to the server icon(by right clicking the SASApp server icon and selecting properties&amp;gt;authorization and adding the user group with deny in all permissions) this denies access and permission of users on all dirs, libraries and datasets.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 14 Nov 2018 09:28:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/New-SAS-User/User-Roles-and-How-to-restrict-server-access-from-user-group/m-p/512866#M2454</guid>
      <dc:creator>PhiSlogan</dc:creator>
      <dc:date>2018-11-14T09:28:55Z</dc:date>
    </item>
    <item>
      <title>Re: User Roles and How to restrict server access from user group</title>
      <link>https://communities.sas.com/t5/New-SAS-User/User-Roles-and-How-to-restrict-server-access-from-user-group/m-p/512883#M2465</link>
      <description>&lt;P&gt;If you want to prevent users from writing to/reading from a specific location on the server, you either have to restrict them from using the relevant code elements (impractical, as these are needed for eg import/export tasks), or you have to make sure that those locations are made secure on the operating system level.&lt;/P&gt;
&lt;P&gt;Library permissions can be handled in SAS metadata, but in order to make them "stick" you need to define those libraries as "metadata bound". Otherwise executing a simple libname can always undercut the metadata, unless you also restrict permissions on the OS level (see above).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;My preferred path is to use the proper permissions in the operating system. If a user does not have read/execute permissions on the directory of a library, a libname for that directory will fail, and the library will not appear in the server list.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Note that relying on third-party tools (SAS in this case) to keep your operating system safe is foolish at best. Use the tools provided by the system itself (see Maxims 14 &amp;amp; 15).&lt;/P&gt;</description>
      <pubDate>Wed, 14 Nov 2018 09:55:00 GMT</pubDate>
      <guid>https://communities.sas.com/t5/New-SAS-User/User-Roles-and-How-to-restrict-server-access-from-user-group/m-p/512883#M2465</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2018-11-14T09:55:00Z</dc:date>
    </item>
  </channel>
</rss>

