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
No comments:
Post a Comment