ReportBuilder authentication

I am using the Report Builder in my application. When it is opened from an environment where there is no proxy, it is asking for authentication and it is working properly.

But when it is opened from the client environment where there is proxy, it is not asking for authentication and he cannot select or view any source of data.

How can I force the Report Builder in the client environment to prompt for authentication? If this cannot work, is there any other possible solution? (Not that it is not allowed to open the port)

Thank you in advance.

Hi,

As you mentioned, the only difference is set the proxy or not, right? Based on my knowledge, I don't think it would affect the behavior of Forms Authentication.

Could you help to check on the following points:

? If you use Forms Authentication, anonymous access must be enabled on the report server virtual directory in Internet Information Services (IIS).
? ASP.NET authentication must be set to Forms. You configure ASP.NET authentication in the Web.config file for the report server.
? Reporting Services can authenticate and authorize users with either Windows Authentication or custom authentication, but not both. Reporting Services does not support simultaneous use of multiple security extensions.

Thanks.

|||

Will that affect the reports?

|||

Hi,

? If you use Forms Authentication, anonymous access must be enabled on the report server virtual directory in Internet Information Services (IIS).
? ASP.NET authentication must be set to Forms. You configure ASP.NET authentication in the Web.config file for the report server.
? Reporting Services can authenticate and authorize users with either Windows Authentication or custom authentication, but not both. Reporting Services does not support simultaneous use of multiple security extensions.

These actions take effect on the reporting servcie site level. It's for the security on reporting servcie site. So it won't affect the detail reports.

Thanks.

sql

Report server asking for credentials again and again (3 times)

I am trying to access reports using custom web application. This application will run under user who have permission to view the reports. When multiple users are accessing reports, if we try to open any report from web application, after some time (around 7-8 mins.) report server is popping up credentials window and if we provide credentials, it is again giving credentials pop up after 5 mins. and after retrying 3 times like this, reports throws error saying 'You are not authorized to view page'. Is there any time out period specified for reports?

As per my investigation, report server default timeout is '30' minutes. I have not changed any values in Report server config files(rsreportserver.config). Nowhere I found that after 5 mins. the credentials pop up should opened?

Any help in this regard, greatly appreciated.

This doesn't sound like a timeout related issue but a security problem. The credentials window will pop up when the server tells the browser that it doesn't have authorization, and the browser gives you three changes to enter the proper credentials. I'm not sure why this would work when the application starts and then start failing after a period of time. If you go directly to the report on the reportserver, do you have the same problem?

|||

For queries which takes less time, reports are running fine. But for long running queries, after 5 mins. around, it is prompting for credentials. This prompting will continue for 2-3 times and atlast page throws message 'You are not authorized to view this page'.

I checked in IIS application pool properties, under which reporting services runs. I found 'TimeSetting Period' under Health tab as 5 mins. Is this the one caused to prompt for credentials for every 5 mins?

Configuration: Sql 2005 Reporting Services, IIS 6.0, Windows 2003

|||

We could able to find the reason why this is happening. We have 2 web servers for Reporting and these 2 boxes runs under Load balancer with BIG-IP. There is timeout value set at TCP Profiler in VIP. Now this has been changed and every thing is running fine.