April 29, 2005 at 1:03 am
I've been going around and around.
I can use to Reporting Services on the local server, but when ever I try to get another client, ie another machine to access Reporting Services it offers the challenge response, I have added groups and roles to the database, including iusr_???? to SQL server and then in to Reporting Services and made sure that the user has full access to the databases.
But I will get challenge response.
I have look through BOL and also got SQL Server Reporting Services by Wrox and Hitchhiker's Guide to SQL Server 2000 Reporting Services, but I am still at a loss.
Does any one know of a step by step guide to Security with Reporting Services?
<<<Bryan>>>
May 2, 2005 at 8:00 am
This was removed by the editor as SPAM
May 2, 2005 at 4:56 pm
At this time, all of our reports are viewed internally within the firewall. I was having the same issue that you describe. Try adding the server to the list of trusted sites ('Tools | Internet Options | Security') in the clients' browser... This allowed others to view reports that I was beta-testing prior to deployment.
-robert
May 2, 2005 at 11:56 pm
I've now got the security working within the Domain, but I've also read that if you want it to work on the Internet you can only have one level of security, but I have heard that you can use MSN Passport to login but I have not tried it yet.
May 4, 2005 at 11:38 pm
You have to define your users or Groups on Active Directory, then using internal RS security tab you can define first: profiles and after users that you want to include in one profile.
i hope this helps, Felix.
September 10, 2005 at 8:35 pm
But what if I don't want to define any security at all? I just want to serve up the report? I tried impersonate but that fails too, it looks like the app gets my domain login and uses that although it is supposed to use iusr since the report is being called from within an dotnet website
September 13, 2005 at 12:39 am
I would never recommend this, but if you really, really want anyone to have access to your reports:
with Windows 2000 & IIS 5, [server]\ASPNET needs access.
with Windows 2003 & IIS 6, NT AUTHORITY\NETWORK SERVICE needs access
They both need rights to Reports, ReportServer as well as your data to serve up your pages.
I hope this is of some help to you.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply