Yes this is still the case for Sitefinity 4.0 which BETA 2 release is out and you can test how permissions work.]
Hiding Libraries based on Roles
provided an idea about how you can secure your content. There are many cases that are not covered and this is a blog post not a code base, so it is normal that not all aspects are affected.
1.You can protect all files from direct access by using a standard ASP.NET HttpHandler or handler that inherits from ContentHttpHandler class. Inside the begin request you can check the current principal and from where the request comes from then decide whether to allow file access or not.
2. Hiding libraries in ListView. Possible solution would be replacing the default view
and binding the grid or thumbs manually, then set the proper pager depending on the libraries that a given role should see.
// set up paging
Pager1.SelectedPage = Pager2.SelectedPage =
Pager1.PageCount = Pager2.PageCount = (
)FilteredLibraries / (
binding the GridView
AllLibrariesGrid.DataSourceID = FilteredDataSource;
AllLibrariesRepeater.DataSourceID = FilteredDataSource;
You could try to subscribe for ItemDataBound or RowCreate events of the GridView from the template where you could also disable
some of the roles and this will not require replacing the base view.
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Public Issue Tracking
system and vote to affect the priority of the items