Try setting up a different host name for each site, then use
host-headers in IIS to differentiate the SRS site from others. This
should allow you to reconfigure all sites to use the default SSL port
(443) instead of having to specify the port.

HTH,

Lance
http://www.lance-hunt.net/

Hi everybody,

Bit of a tricky question...

I'm running RS2K on IIS 6.0 in a nondefault website which I've secured with
a certificate. There is already one website with SSL on the server, hence,
because of the limitation in the TLS stack, this website runs on port 563,
which is also a well known port for SSL and gets recognized by IE.

I got everything working up to the point where I can't switch on the
"Require Secure Channel (SSL)" option in the properties of the website as
this seems to break things. I have the http:// pointers in the config files
set to http:// (rather then https://) but various experiments did not finish
successfully.

Accessing the website I have to use https://reporting.test.lab:563/reports -
that means the port has to be explicit (as opposed to any other websites
running on this port which gets picked up automatically).

I'll stop rambling on now, but would appreciate any suggestions if anybody's
done this before.

thanks

rad

Hi Lance,

thanks for the suggestion, but that's not how SSL operates. Because the
information is encrypted, you can only distinguish by IP addresses or ports,
host headers don't come into play at all; however an idea could be using two
IP addresses....

Thanks,

Rad

[quoted text, click to view]

See MSDN:

Configuring SSL Host Headers (IIS 6.0)
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/596b9108-b1a7-494d-885d-f8941b07554c.mspx

However, the IP-based approach is definitely an easier option.

Lance Hunt
http://www.lance-hunt.net

Further investigation revealed that for the SSL Secure Connection to work
properly and the Require SSL connection to be checked the
SecureConnectionLevel has to be set to 3


[quoted text, click to view]