Friday, March 23, 2012

report viewer and reporting services security

i have a web application in studio 2005 using the report viewer control. i have my own security model implemented on my web pages for clients [1..n] each of the [1..n] clients should be able to view reports of their order history. i have the report viewer set up in url mode. the question is that when i have drill downs in my final reports, a user with some tech knowledge, would be able to obtain the url to my sql server running reporting services.

the sql server will not be given a port 80 acess. how do i go about displaying reports without any savvy user being able to locate the server locations/credentials?

i donot want to create windows account for each [1..n] clients as this is ever growing

If by "url mode" you mean hyperlinks pointing to the report URL address, you should rethink your approach. Instead, consider server-side report generation. In this case, SSRS does reasonable job to protect the parameters as you can see by inspecting the drilldown hyperlinks.|||

Teo, thats what i mean. How would i go about the approach that you are suggesting?

- would i have to create subscriptions to generate the reports and save them to disk?

\

|||If i am to use SOAP then the interactive features are not availabe as this read up provides that info:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnhcvb04/html/vb04k8.asp|||You will host the VS.NET 2005 ReportViewer control on your ASP.NET page and bind it to the server report. If you are new to the Report Viewer control, you may find the following article useful.|||I did read the article but from read ups, the drill down interactive feature is lost when using SOA/web services to gerenate report in 'remote mode'. is that statetment true? if not then i guess this would work out well|||This is incorrect. SSRS 2005 enhances the web service APIs to support interactive features so interactive featues will work with the VS.NET ReportViewer.

No comments:

Post a Comment