Reporting Services authorisation, authentification

Question

I would like to use Reporting Services in our business application. I'm new with it and I'm not sure can we do it or not. We are using SQL Server authentification and our stored procedure retrives different information for different users (users have
pseudopriveleges on tables rows), so our report server should go the same way. I've read some information about custom authentification and want to ask - If I login to SSRS with custom username and password how this credentials could
be used in Report DataSources? What type of authentification should I select in Data Source? Does SSRS automaticaly send user credentials to datasources?
Thanks for reading :-)

Answer 1

I see.
Those constraints were not clear from your original question.
Thank you for clarifying.
A bit more clarification is required, though:
Do you plan to use SSRS embedded in your application (by using the Reporting Services API)?
If so, you might find it easier to simply deliver an additional parameter to your reports which would serve as a sort of "User Token" (like "UserID" for example), so that your reporting queries would know which user is querying them;
and the "User Token" will be delivered by your application code - hidden away from the user. Based on this "User Token", you might want to use
impersonation for your existing procedures to work properly.
Please note that you'd might want to use SSL in order to encrypt your traffic over the network in such a case.
Also note that I'm only suggesting these convoluted suggestions because you mentioned that it must be SQL Authentication. If you'd accept Windows Authentication, you'd be able to use the built-in Windows NT authentication mechanism which would be much easier
for you to implement in your reports.
Eitan Blumin; SQL Server Consultant - Madeira Data Solutions;