<?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 MDX for authorization in a cube in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/MDX-for-authorization-in-a-cube/m-p/327299#M7158</link>
    <description>&lt;P&gt;I have an MDX statement which works on a hierachie and is supposed to show certain groups ony the data they are allowed to see. Some Users are also in groups that are not allowed to see any data in this cube but have some other groups that are allowed to see data.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;My statement works finde as long as the user only has groups that are allowed to see at least some data. If the user also has a group that isn't allowed to see any data I get an &lt;STRONG&gt;data set is empty error&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I need the user to still be able to see the data he is allowed to see, even though he has groups that aren't allowed to see data. Is there way to achieve this?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
    <pubDate>Wed, 25 Jan 2017 09:33:56 GMT</pubDate>
    <dc:creator>Criptic</dc:creator>
    <dc:date>2017-01-25T09:33:56Z</dc:date>
    <item>
      <title>MDX for authorization in a cube</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/MDX-for-authorization-in-a-cube/m-p/327299#M7158</link>
      <description>&lt;P&gt;I have an MDX statement which works on a hierachie and is supposed to show certain groups ony the data they are allowed to see. Some Users are also in groups that are not allowed to see any data in this cube but have some other groups that are allowed to see data.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;My statement works finde as long as the user only has groups that are allowed to see at least some data. If the user also has a group that isn't allowed to see any data I get an &lt;STRONG&gt;data set is empty error&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I need the user to still be able to see the data he is allowed to see, even though he has groups that aren't allowed to see data. Is there way to achieve this?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Wed, 25 Jan 2017 09:33:56 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/MDX-for-authorization-in-a-cube/m-p/327299#M7158</guid>
      <dc:creator>Criptic</dc:creator>
      <dc:date>2017-01-25T09:33:56Z</dc:date>
    </item>
    <item>
      <title>Re: MDX for authorization in a cube</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/MDX-for-authorization-in-a-cube/m-p/327715#M7204</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I believe what you might "hit" here are conflicting permissions where deny simply takes precedence.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When you have denies and grants at the same time, the deny will always take precedence.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Maybe someone else has some ideas on it, but I am thinking that you might have to restructure and rethink the way your groups are being set up.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You cannot have one user in two different groups where one group has a grant and the other a deny.&lt;/P&gt;
&lt;P&gt;The option to grant would be to assign permissions to this user directly, as a direct ACE will take precedence over group permissions.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To give an example:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Dataset A&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;User X is in group A … DENY on data set A for group A&lt;/P&gt;
&lt;P&gt;User X is in group B … GRANT on data set A for group B&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Assign user X explicitly to data set A and grant permissions. With the explicit ACE on the data set, all permissions for user X in groups are overwritten as the explicit Grant takes precedence.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You might be familiar with this, but if not, you might find this helpful:&lt;/P&gt;
&lt;P&gt;&lt;A href="http://support.sas.com/documentation/cdl/en/bisecag/69827/HTML/default/viewer.htm#n0pt0r7u55rqu2n1cdu2wvt47j78.htm" target="_blank"&gt;http://support.sas.com/documentation/cdl/en/bisecag/69827/HTML/default/viewer.htm#n0pt0r7u55rqu2n1cdu2wvt47j78.htm&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Would it makes sense to maybe restructure your groups and the members of the groups?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best&lt;/P&gt;
&lt;P&gt;Anja&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Jan 2017 13:35:27 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/MDX-for-authorization-in-a-cube/m-p/327715#M7204</guid>
      <dc:creator>anja</dc:creator>
      <dc:date>2017-01-26T13:35:27Z</dc:date>
    </item>
    <item>
      <title>Re: MDX for authorization in a cube</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/MDX-for-authorization-in-a-cube/m-p/327915#M7213</link>
      <description>&lt;P&gt;Because these can be quite tricky to troubleshoot, and there are a number of different ways&amp;nbsp;this can be done, perhaps you can post a concrete example (changing names/values as appropriate to protect privacy) for an individual where it is failing including:&lt;/P&gt;
&lt;P&gt;1) The identity heirarchy for the individual showing which groups they are a member of an how they are a member - this is used to prioritize access controls.&lt;/P&gt;
&lt;P&gt;2) All relevent permission conditions&amp;nbsp;that have been applied to the dimension for any of the groups in the individuals identity hierarchy (including SASUSERS and PUBLIC)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Additionally, we have a (commercial) Metacoda Permissions Tracer plug-in that can show all of the relevant (and irrelevant) permissions (and permission conditions) for a user's access to a cube dimension including precedance info based on access control type and identity hierarchy levels. I'd be happy to walk you through it via a web meeting if you want to try it out.&lt;/P&gt;</description>
      <pubDate>Fri, 27 Jan 2017 02:46:15 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/MDX-for-authorization-in-a-cube/m-p/327915#M7213</guid>
      <dc:creator>PaulHomes</dc:creator>
      <dc:date>2017-01-27T02:46:15Z</dc:date>
    </item>
    <item>
      <title>Re: MDX for authorization in a cube</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/MDX-for-authorization-in-a-cube/m-p/328226#M7221</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/50279"&gt;@Criptic&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;yours is a good question that any SAS Administrator should be aware of.&lt;/P&gt;
&lt;P&gt;Full documentation of SAS Administration: security&amp;nbsp;&lt;A href="http://support.sas.com/documentation/cdl/en/bisecag/69827/PDF/default/bisecag.pdf" target="_blank"&gt;http://support.sas.com/documentation/cdl/en/bisecag/69827/PDF/default/bisecag.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As explained by both&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/18432"&gt;@PaulHomes&lt;/a&gt;&amp;nbsp;and&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/25908"&gt;@anja&lt;/a&gt;, indeed, when there is a conflic on metadata permissions at the same level of security, for security reasons the deny setting takes precedence.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To easen your read task, I reccommend you some basics:&lt;/P&gt;
&lt;P&gt;A good start on Security:&amp;nbsp;&lt;A href="http://support.sas.com/resources/papers/proceedings16/10962-2016.pdf" target="_blank"&gt;http://support.sas.com/resources/papers/proceedings16/10962-2016.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;One security model that will help you to avoid those situations in the future, the Danish model:&amp;nbsp;&lt;A href="http://support.sas.com/resources/papers/proceedings11/376-2011.pdf" target="_blank"&gt;http://support.sas.com/resources/papers/proceedings11/376-2011.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;All in all, if you cannot get used to the security, I would take the advise from&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/18432"&gt;@PaulHomes&lt;/a&gt;&amp;nbsp;about the Metacoda tool (a great one), or ask for consulting services to help you.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;PS. did you had the opportunity to google a bit or even search in the communities before posting? Here is a similar question answered already, and there are many more.&amp;nbsp;&lt;A href="https://communities.sas.com/t5/General-SAS-Programming/Metadata-permissions-conflict/td-p/195482" target="_blank"&gt;https://communities.sas.com/t5/General-SAS-Programming/Metadata-permissions-conflict/td-p/195482&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best,&lt;/P&gt;
&lt;P&gt;Juan&lt;/P&gt;</description>
      <pubDate>Sat, 28 Jan 2017 15:23:13 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/MDX-for-authorization-in-a-cube/m-p/328226#M7221</guid>
      <dc:creator>JuanS_OCS</dc:creator>
      <dc:date>2017-01-28T15:23:13Z</dc:date>
    </item>
    <item>
      <title>Re: MDX for authorization in a cube</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/MDX-for-authorization-in-a-cube/m-p/328330#M7225</link>
      <description>&lt;P&gt;You got me on the right track. Thank you!&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jan 2017 07:27:19 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/MDX-for-authorization-in-a-cube/m-p/328330#M7225</guid>
      <dc:creator>Criptic</dc:creator>
      <dc:date>2017-01-30T07:27:19Z</dc:date>
    </item>
    <item>
      <title>Re: MDX for authorization in a cube</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/MDX-for-authorization-in-a-cube/m-p/328331#M7226</link>
      <description>Thank you for your answer. The Plug-In sounds interesting but I was able to solve my problem, so right now I'm not interested but I'll keep it mind.</description>
      <pubDate>Mon, 30 Jan 2017 07:28:20 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/MDX-for-authorization-in-a-cube/m-p/328331#M7226</guid>
      <dc:creator>Criptic</dc:creator>
      <dc:date>2017-01-30T07:28:20Z</dc:date>
    </item>
    <item>
      <title>Re: MDX for authorization in a cube</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/MDX-for-authorization-in-a-cube/m-p/328333#M7227</link>
      <description>&lt;P&gt;Thank you for the guide, it will be helpful on reading up on the matter!&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jan 2017 07:28:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/MDX-for-authorization-in-a-cube/m-p/328333#M7227</guid>
      <dc:creator>Criptic</dc:creator>
      <dc:date>2017-01-30T07:28:55Z</dc:date>
    </item>
  </channel>
</rss>

