Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums  SQL Server 2005 Forums  Other SQL Server Topics (2005)  Turning off impersonation on a SQL Server datasour

Author  Topic  canuck81 Starting Member 1 Post Posted - 2007-11-05 : 10:47:31 Dear SQL Server Reporting Services Support Guru, How do we configure Reporting Services such that when it attempts to connect to a datasource (e.g. Microsoft SQL Server datasource), it connects as the service account under which it is running as opposed to the calling user? From our research we were thinking we could try one of two things: 1) change the credential type on the datasource itself so that it does not use Windows Integrated Security and instead connects as itself or 2) change the <identity impersonate="true"> flag in the web.config of the ReportServer web service to false. A high level description of our architecture is that we have a client application with an web browser control that displays a report in the ReportViewer web control on the server. The report uses a SQL Server datasource to connect to our own SQL Server database hosted on the same server as Reporting Services but we want it to turn off impersonation and have Reporting Services connect as itself, not as the calling user. We do not want to grant users in Production direct access to our SQL Server database; so instead we wanted to configure Reporting Services such that it resolves and connects to the datasource using its own credentials. A related question...when does the ReportServer web service get called? For both retrieval of the .rdl files and connecting to the datasource for dataset retrieval? What exactly does that <identity impersonate="true"> flag affect? Any help you can provide would be very much appreciated. Thanks much! -canuck81