I'm looking for some advice on how to protect reports that are ultimately displayed in ASPX pages. I have developed a Silverlight 3 application. Within the application, I am able to execute a report, and display this report in an HtmlPlaceholder or a seperate browser window. Because this report is embedded within an ASPX page, anyone can simply type in the URL for the report (www.MyWebSite.com/MyReport.aspx) and cause the report to be generated. These reports contain sensitive data, so I want to make sure that the pages are authenticated appropriately before they can be accessed. Any suggestions on how to accomplish this?
My environment is IIS 7, my Silverlight 3 application, plus the reports (each embedded in its own ASPX page). These are anonymous users that must log into my Silverlight 3 application. I do not wnat users to be able to access the ASPX pages without going through the SL3 app.
My environment is IIS 7, my Silverlight 3 application, plus the reports (each embedded in its own ASPX page). These are anonymous users that must log into my Silverlight 3 application. I do not wnat users to be able to access the ASPX pages without going through the SL3 app.