Configuring SQL Reporting Services for SSL

I've got an issue that is perhaps a bit different than any other
related posting on this topic.
I have successfully installed and configured SSRS for SQL 2005 and now
I'm at the step where I need to require SSL. So I opened the
Reporting Services Configuration, then selected Report Server Virtual
Directory. Then I select the checkbox Require Secure Socket Layer
(SSL) connections. At this step I am required to enter the name of
the certificate. Here is the problem: The server in on 2 seemingly
different domains and the certificate was issued to domain A, but the
server name is listed under domain B, but both domains resolve to the
same IP address. Here are the specifics:
A) The cert was named according to this domain pattern:
<server_name>.orgA.domainA.com
B) The computer name in system properties is:
<server_name>.orgB.xx.domainB.com
When I run the report server web interface, I get this error "The
request failed with HTTP status 401: Unauthorized."
So my question is: Why isn't the certificate for Domain A working?
Should I request a certificate under the domain of option B above? Is
there a configuration that is required? Note - I've modified the file
rsreportserver.config per the installation instructions.
Thanks in advance for your assistance,
-ScottOn Mar 6, 10:33 am, scottdistef...@.gmail.com wrote:
> I've got an issue that is perhaps a bit different than any other
> related posting on this topic.
> I have successfully installed and configured SSRS for SQL 2005 and now
> I'm at the step where I need to require SSL. So I opened the
> Reporting Services Configuration, then selected Report Server Virtual
> Directory. Then I select the checkbox Require Secure Socket Layer
> (SSL) connections. At this step I am required to enter the name of
> the certificate. Here is the problem: The server in on 2 seemingly
> different domains and the certificate was issued to domain A, but the
> server name is listed under domain B, but both domains resolve to the
> same IP address. Here are the specifics:
> A) The cert was named according to this domain pattern:
> <server_name>.orgA.domainA.com
> B) The computer name in system properties is:
> <server_name>.orgB.xx.domainB.com
> When I run the report server web interface, I get this error "The
> request failed with HTTP status 401: Unauthorized."
> So my question is: Why isn't the certificate for Domain A working?
> Should I request a certificate under the domain of option B above? Is
> there a configuration that is required? Note - I've modified the file
> rsreportserver.config per the installation instructions.
> Thanks in advance for your assistance,
> -Scott
Anybody thoughts?|||On Mar 6, 11:33 am, scottdistef...@.gmail.com wrote:
> I've got an issue that is perhaps a bit different than any other
> related posting on this topic.
> I have successfully installed and configured SSRS for SQL 2005 and now
> I'm at the step where I need to require SSL. So I opened the
> Reporting Services Configuration, then selected Report Server Virtual
> Directory. Then I select the checkbox Require Secure Socket Layer
> (SSL) connections. At this step I am required to enter the name of
> the certificate. Here is the problem: The server in on 2 seemingly
> different domains and the certificate was issued to domain A, but the
> server name is listed under domain B, but both domains resolve to the
> same IP address. Here are the specifics:
> A) The cert was named according to this domain pattern:
> <server_name>.orgA.domainA.com
> B) The computer name in system properties is:
> <server_name>.orgB.xx.domainB.com
> When I run the report server web interface, I get this error "The
> request failed with HTTP status 401: Unauthorized."
> So my question is: Why isn't the certificate for Domain A working?
> Should I request a certificate under the domain of option B above? Is
> there a configuration that is required? Note - I've modified the file
> rsreportserver.config per the installation instructions.
> Thanks in advance for your assistance,
> -Scott
I'm sorry to pester, but I'm running out of things to try on this
issue. Does anyone have thoughts to share on requiring SSL with SQL
2005 Reporting?