Sorry to revive a previously discussed point, I've been trying to get my head around the http://msdn.microsoft.com/library/?url=/library/en-us/dnsql2k/html/ufairs.asp?frame=true#ufairs_topic3 article given in a previous post. I think this is the solution we require but it raises a few issues that I would like some help on. What we are trying to do, is when the user logs on to the .net application, he is authenicated on the report server at the same time. So the user only sees one authenication process and is assigned a role from the report server to limit his/her access to reports. The user credentials at the moment are kept separate to the reportserver, i.e a different datasource and this will be modified slightly to include the report server role mappings. Access to reports is done using a slightly customised ReportViewer control included with SRS.
1. In the development environment we obviously publish different reports for differing clients. These reports are driven from differing databases and so are the user credentials for the application. Is it possible to develop a solution to encapsulate this need? I was thinking of one security extension that accepts the name of the application as a parameter and changes behaviour based on that. I'll probably use the authority parameter?
If I have completely missed the point here, please let me know!!!
Thanks in advance,
Mike.You could store the credentials required for each report in the report server.
And you could give selective permissions to the various folder/reports in the server.
Would that satisfy the requirements?
Thanks
Tudorsql
No comments:
Post a Comment