Monday, March 19, 2012

How to use Reporting Services without enforcing SSL?

Hello,

I have a reporting services application that needs to run reporting services without a user context. However, it will not pass the SSL check. I am using a self-signed certificate that is in the trusted certificates store. What I would really like to do is run reporting services without enforcing SSL (just not allow port 80 connections from the firewalll for security) and merely allow SSL connections when they come in so that any local programs can use reporting services without the need for SSL. As far as I know, Reporting Services (ISAPI filter?) is somehow checking the http headers and not allowing, at least an anonymous, a connection *unless* SSL is forced (WHY?). If my app redirects using the https://FQDN or http://localhost to reporting services it fails the SSL check.

Is there a way around this or can simply do something with the certificate store, like trusted certificates or publishers, so that my local programs can pass the SSL check?

You can use the Reporting Services Configuration tool to set whether the Report Server requires SSL. See the doc: http://msdn2.microsoft.com/en-us/library/ms345223.aspx. Does this answer your question?

-Albert

No comments:

Post a Comment