The short story... We need to be able to access reports using an impersonated account from our application.
The longer version...
We received a mandate that we need to tighten report security down to the point where access is defined all the way down to the report level, by user.
The decision was made to control report access though our primary application (as opposed to the Report Manager) and to use a service account with "Browser" access to return the called report.
The problem is that we are having a hell of a time getting it to work...
Well... We sorta had it working, using the Microsoft Report Viewer for ASPX (v3.5), using version 10 of the Microsoft.ReportViewer.WebForms, Microsoft.ReportViewer.Winforms and Microsoft.ReportViewer.Common assemblies...
<rsweb:ReportViewer ID="ReportViewer1" runat="server" Width="100%" ProcessingMode="Remote" AsyncRendering="true" SizeToReportContent="false" Height="825px" />
But the performance was horrible so we had to go back to calling the report via URL.
If anyone's been able to either, call a report using impersonation through IE OR, failing that, knows what parameter setting need to be tweaked in the ReportViewer control to get good performance, please let me know. Any ideas or assistance would be greatly appreciated.
Thanks in advance,
Jason
Jason Long