<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Implementing Data Security in a Report Model</title><link>http://blogs.msdn.com/bobmeyers/pages/Implementing-Data-Security-in-a-Report-Model.aspx</link><description>The report models introduced in SQL Server 2005 feature a number of ways to customize the data visible to different users and groups: perspectives, model item security, security filters, and opaque expressions. This article describes when and how to use</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Article: Implementing Data Security in a Report Model</title><link>http://blogs.msdn.com/bobmeyers/pages/Implementing-Data-Security-in-a-Report-Model.aspx#554512</link><pubDate>Sat, 18 Mar 2006 21:08:01 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:554512</guid><dc:creator>Bob's SQL Reporting Services Blog</dc:creator><description>I just posted&amp;amp;amp;nbsp;the first&amp;amp;amp;nbsp;article on my blog. Here's the abstract:&lt;br&gt;The report models introduced...</description></item><item><title>Implementing Data Security in a Report Model</title><link>http://blogs.msdn.com/bobmeyers/pages/Implementing-Data-Security-in-a-Report-Model.aspx#554623</link><pubDate>Sun, 19 Mar 2006 02:54:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:554623</guid><dc:creator>Prologika</dc:creator><description>Bob Meyers (the mastermind behind the RS 2005 Report Builder) tells us how to implement horizontal data...</description></item><item><title>Good post on Model Security</title><link>http://blogs.msdn.com/bobmeyers/pages/Implementing-Data-Security-in-a-Report-Model.aspx#555495</link><pubDate>Mon, 20 Mar 2006 16:38:11 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:555495</guid><dc:creator>Russell Christopher's Semi-Useful BI Musings</dc:creator><description>Bob Meyers posted a really good write-up on various ways to secure your report model!&lt;br&gt;&lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/bobmeyers/articles/Implementing_Data_Security_in_a_Report_Model.asp"&gt;http://blogs.msdn.com/bobmeyers/articles/Implementing_Data_Security_in_a_Report_Model.asp&lt;/a&gt;...</description></item><item><title>re: Implementing Data Security in a Report Model</title><link>http://blogs.msdn.com/bobmeyers/pages/Implementing-Data-Security-in-a-Report-Model.aspx#583355</link><pubDate>Tue, 25 Apr 2006 20:21:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:583355</guid><dc:creator>bell.joshua</dc:creator><description>FYI... The URL listed in one of the prior responses does not work for me. (&lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/bobmeyers/articles/Implementing_Data_Security_in_a_Report_Model.asp"&gt;http://blogs.msdn.com/bobmeyers/articles/Implementing_Data_Security_in_a_Report_Model.asp&lt;/a&gt;)&lt;br&gt;&lt;br&gt;My question:&lt;br&gt;Is it possible to use Active Directory groups (or Organizational Units) to assign security filters? The original post outlines the method for retrieving the current user ID, but is there a way to determine whether or not the current user is in a particular group?&lt;br&gt;&lt;br&gt;If not, I think this would be a good enhancement to include in the next Report Builder release.</description></item><item><title>re: Implementing Data Security in a Report Model</title><link>http://blogs.msdn.com/bobmeyers/pages/Implementing-Data-Security-in-a-Report-Model.aspx#583401</link><pubDate>Tue, 25 Apr 2006 21:10:21 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:583401</guid><dc:creator>bell.joshua</dc:creator><description>Well... disregard the URL comment in my previous post. The URL was truncated in the preview (ends in .asp instead of .aspx), and when I added the 'x', I realized that it was the URL for this page anyway.&lt;br&gt;&lt;br&gt;/sigh&lt;br&gt;&lt;br&gt;</description></item><item><title>re: Implementing Data Security in a Report Model</title><link>http://blogs.msdn.com/bobmeyers/pages/Implementing-Data-Security-in-a-Report-Model.aspx#7895143</link><pubDate>Mon, 25 Feb 2008 21:36:07 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7895143</guid><dc:creator>Krip</dc:creator><description>&lt;p&gt;Having some trouble getting Security Filters to work. &amp;nbsp;I've added a filter to an entity and deployed the Report Model, but still see all data when running a report. &amp;nbsp;Is there some other setting I'm missing?&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Krip&lt;/p&gt;
</description></item><item><title>Implementing Data Security in a Report Model Using Folder Namespace</title><link>http://blogs.msdn.com/bobmeyers/pages/Implementing-Data-Security-in-a-Report-Model.aspx#9463579</link><pubDate>Sat, 07 Mar 2009 01:51:58 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9463579</guid><dc:creator>boumerlin</dc:creator><description>&lt;p&gt;I have some questions regarding report model security and folder namespaces. Perhaps you can help me out? Shouldn't I be able to prevent a user from viewing/accessing a model based on folder security settings on the report server? I'm having difficulty implementing this so that User_1 can only view the model for Client_A and User_2 the model for Client_B. Client_A and Client_B each have their own folder structure. &lt;/p&gt;
&lt;p&gt;I'm using Forms Authentication and right now, once a user is Authenticated, the user has carte blanche to the report models with the ability to see the models and access them.&lt;/p&gt;
</description></item></channel></rss>