asked
Error While Passing Credentials from SSRS to Sharepoint Data Source
I am using SSRS 2008 R2 to build a report that uses a Sharepoint list as its data source, to which it is configured to connect using Windows Authentication (Integrated Security). The problem is that when the report is deployed to the Report Server, the SharePoint source rejects the credentials, returning: ----------------- An error has occurred during report processing. (rsProcessingAborted) Query execution failed for dataset 'ListDataset'. (rsErrorExecutingCommand) An error occurred when accessing the specified SharePoint list. The connection string might not be valid. Verify that the connection string is correct. (rsSPDataProviderError) The request failed with HTTP status 401: Unauthorized. -------- The Sharepoint data source accepts my credentials when I test the report locally in BIDS, but does not accept them after they 'double-hop' from the Report Server. What is the best work-around? Do I need to create a Service Account in SSRS, supply those credentials in the data source within SSRS, and grant the necessary read permissions to the Service Account via Sharepoint? Any suggestions would be greatly appreciated.
This issue will be related to the Kerberos Authentication. Ensure, that you have proper Kerberos authentication setup on the side of SSRS and also SharePoint. If it is not properly configured, than correct credentials are not passed and SSRS is accessing the SharePoint under unknown credentials. When you run the report in BIDS, it is working as you do not have a double hop scenario like in the case of SSSRS.
A lot of this depends on what your IT department will let you do In short, I think you have 3 options: 1. create a windows service account (as you alluded to) and use that in the data source 2. create a SQL Account on the target server and use that (presuming you are using mixed authentication mode) 3. Change the configuration on AD for the report server to allow it to delegate authority How you are best to get around it, however, will depend entirely on your environment and its security requirements. I'd discuss this with you AD admin and whoever is in charge of security there
13 People are following this question.
