<?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 Row level security query in SAS Web Report Studio</title>
    <link>https://communities.sas.com/t5/SAS-Web-Report-Studio/Row-level-security-query/m-p/31083#M492</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jamie,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have a small number of relatively static companies, and have those companies users in company groups in metadata, then you could add a number of company filters in the information map and use access controls to force the use of each for its respective company group (&lt;EM&gt;authorization-based prefilter&lt;/EM&gt;).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have a larger number of companies that might also change regularly and the mapping of users to companies is readily available as a data source, then another alternative is to apply a userid based &lt;EM&gt;identity-driven general prefilter&lt;/EM&gt; to a userid-company mapping table as a mandatory table joined to your main table(s) via the appropriate company key.&amp;nbsp; The resulting data returned by the information will be subsetted to the company (or companies) that the logged in userid is associated with. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can find more information about this (for SAS 9.1.3) in the &lt;EM&gt;SAS 9.1.3 Intelligence Platform Security Administration Guide, Second Edition&lt;/EM&gt;, Chapter 10 &lt;A href="http://support.sas.com/onlinedoc/913/getDoc/en/bisecag.hlp/a003073623.htm"&gt;BI Row-Level Permissions&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Depending on your security requirements you may also want/need to consider the possibility of &lt;A href="http://support.sas.com/onlinedoc/913/getDoc/en/bisecag.hlp/a003073626.htm"&gt;mediated data access&lt;/A&gt;. Whilst you might not actually need it, its still worth reading at least to determine whether it is required for your environment or not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;Paul&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 18 Jan 2012 04:07:26 GMT</pubDate>
    <dc:creator>PaulHomes</dc:creator>
    <dc:date>2012-01-18T04:07:26Z</dc:date>
    <item>
      <title>Row level security query</title>
      <link>https://communities.sas.com/t5/SAS-Web-Report-Studio/Row-level-security-query/m-p/31081#M490</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi folks hope you can help&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have just created an info map which has a column named "company". I have created a simple report on WRS which views a table with all companies.&lt;/P&gt;&lt;P&gt;there are about 50 different companies and we have now set up user ids for each one.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible to use row level security on SAS Information Map Studio 3.1 to conditionally show only the companies for certain user IDs?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;&lt;P&gt;Jamie&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jan 2012 11:59:39 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Web-Report-Studio/Row-level-security-query/m-p/31081#M490</guid>
      <dc:creator>Jamie</dc:creator>
      <dc:date>2012-01-17T11:59:39Z</dc:date>
    </item>
    <item>
      <title>Row level security query</title>
      <link>https://communities.sas.com/t5/SAS-Web-Report-Studio/Row-level-security-query/m-p/31082#M491</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;further info: If I create a filter to say show only "Company A" how do I then associate that with a User ID?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks again&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jan 2012 12:02:01 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Web-Report-Studio/Row-level-security-query/m-p/31082#M491</guid>
      <dc:creator>Jamie</dc:creator>
      <dc:date>2012-01-17T12:02:01Z</dc:date>
    </item>
    <item>
      <title>Row level security query</title>
      <link>https://communities.sas.com/t5/SAS-Web-Report-Studio/Row-level-security-query/m-p/31083#M492</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jamie,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have a small number of relatively static companies, and have those companies users in company groups in metadata, then you could add a number of company filters in the information map and use access controls to force the use of each for its respective company group (&lt;EM&gt;authorization-based prefilter&lt;/EM&gt;).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have a larger number of companies that might also change regularly and the mapping of users to companies is readily available as a data source, then another alternative is to apply a userid based &lt;EM&gt;identity-driven general prefilter&lt;/EM&gt; to a userid-company mapping table as a mandatory table joined to your main table(s) via the appropriate company key.&amp;nbsp; The resulting data returned by the information will be subsetted to the company (or companies) that the logged in userid is associated with. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can find more information about this (for SAS 9.1.3) in the &lt;EM&gt;SAS 9.1.3 Intelligence Platform Security Administration Guide, Second Edition&lt;/EM&gt;, Chapter 10 &lt;A href="http://support.sas.com/onlinedoc/913/getDoc/en/bisecag.hlp/a003073623.htm"&gt;BI Row-Level Permissions&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Depending on your security requirements you may also want/need to consider the possibility of &lt;A href="http://support.sas.com/onlinedoc/913/getDoc/en/bisecag.hlp/a003073626.htm"&gt;mediated data access&lt;/A&gt;. Whilst you might not actually need it, its still worth reading at least to determine whether it is required for your environment or not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;Paul&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Jan 2012 04:07:26 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Web-Report-Studio/Row-level-security-query/m-p/31083#M492</guid>
      <dc:creator>PaulHomes</dc:creator>
      <dc:date>2012-01-18T04:07:26Z</dc:date>
    </item>
    <item>
      <title>Row level security query</title>
      <link>https://communities.sas.com/t5/SAS-Web-Report-Studio/Row-level-security-query/m-p/31084#M493</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Paul,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First of all thanks very much for taking the time to reply. Much appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was able to set up a working test using your second suggestion of "&lt;SPAN style="background-color: #ffffff;"&gt;userid based&lt;/SPAN&gt;&lt;EM style="background-color: #ffffff;"&gt;identity-driven general prefilter&lt;/EM&gt;&lt;SPAN style="background-color: #ffffff;"&gt; " however I could only apply this to a data table and not a cube. The edit data item option doesnt seem to be there when using a cube.&amp;nbsp; It worked nicely when using a table though, and I also set up a test security associations table and linked it which also works.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #ffffff;"&gt;I was reading on the sas support site about your first option. I created the filter but when I went into the authorization properties and granted explicit read access, the "Add condition" button is also missing. Again, when usign a data table this option is available, but with the cube it isnt.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #ffffff;"&gt;I was reading into the system and evironment requirements and I noticed that Service Pack 4 is required. I currently am using Service Pack 2. Do you know if its possible that these optiions became available for cubes with the Service pack update?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #ffffff;"&gt;Thanks again for any help, it makes the difference.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Jan 2012 09:52:14 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Web-Report-Studio/Row-level-security-query/m-p/31084#M493</guid>
      <dc:creator>Jamie</dc:creator>
      <dc:date>2012-01-18T09:52:14Z</dc:date>
    </item>
    <item>
      <title>Row level security query</title>
      <link>https://communities.sas.com/t5/SAS-Web-Report-Studio/Row-level-security-query/m-p/31085#M494</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jamie,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For OLAP cubes you need to do the filtering at the level of the OLAP cube itself using OLAP Member Level Security.&amp;nbsp; This is preferable anyway since the security is also applied when you open the cube directly without using an information map (such as from SAS Enterprise Guide).&amp;nbsp; The documentation for this is also in the SAS 9.1.3 Intelligence Platform Security Administration Guide, Second Edition under &lt;A href="http://support.sas.com/onlinedoc/913/getDoc/en/bisecag.hlp/a003139255.htm"&gt;OLAP Member-Level Permissions&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know in SAS 9.2 you can also use identity-driven substitutions in the MDX filter expression, but I am not sure about SAS 9.1.3.&amp;nbsp; I did a blog post on this topic for SAS 9.2 a while back: &lt;A href="http://platformadmin.com/blogs/paul/2011/01/sas92-olap-cube-identity-driven-member-level-security/"&gt;SAS 9.2 OLAP Cube Identity Driven Member Level Security&lt;/A&gt;.&amp;nbsp; The post contains a few MDX examples and there are some useful comments by others too.&amp;nbsp; It has been a while since I have done OLAP Member Level Security in SAS 9.1.3 so I am not sure if identity-driven substitutions were available in SAS 9.1.3 or if they were new in SAS 9.2.&amp;nbsp; I can't find any references to them for OLAP member level security in the SAS 9.1.3 docs, but who knows... it might be worth giving it a try.&amp;nbsp; Perhaps someone else might be able to confirm whether SAS 9.1.3 supports this or not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;Paul&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Jan 2012 12:02:20 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Web-Report-Studio/Row-level-security-query/m-p/31085#M494</guid>
      <dc:creator>PaulHomes</dc:creator>
      <dc:date>2012-01-18T12:02:20Z</dc:date>
    </item>
    <item>
      <title>Row level security query</title>
      <link>https://communities.sas.com/t5/SAS-Web-Report-Studio/Row-level-security-query/m-p/31086#M495</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Paul, thats very helpful indeed.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Jan 2012 12:19:09 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Web-Report-Studio/Row-level-security-query/m-p/31086#M495</guid>
      <dc:creator>Jamie</dc:creator>
      <dc:date>2012-01-18T12:19:09Z</dc:date>
    </item>
  </channel>
</rss>

