Does anyone know how to configure SSRS 2008's Report Manager to use a host header over SSL? I could do it in SSRS 2005 because it was hosted on IIS, using: cscript.exe adsutil.vbs set /w3svc/%1/SecureBindings ":443:%2"(Where %1 is the site identifier and %2 is the host header name.) However, now that it is off IIS, I can't seem to get it to work.
Welcome to the forums. Have you checked: http://sqlskills.com/blogs/stacia/post/SQL-Server-2008-Reporting-Services-Configuration-Changes.aspx & http://boolean1.syncratec.com/2008/09/using-host-headers-and-ssl-https-in-iis-60.html
Thanks, Satya. I've read the articles, but they didn't seem to have the answer...I did some tests and it is behaving as though HTTP.SYS is not listening on port 443. Here is an example of what I've tried. (I've replaced the names, but the pattern is the same.)Machine name: colo-test1 External url: test1.testdomain.org Wildcard certificate: *.testdomain.orgIn the Report Manager URL section of the Reporting Services Configuration Manager, I clicked the Advanced button, and then the Add button to add a host header to the "Multiple Identities for Report Manager" section: Host Header Name: test1.testdomain.org TCP Port: 80 I clicked the Add button under the "Multiple SSL Identities for Report Manager" and selected the following options: IP Address: (All IPv4) SSL Port: 443 Certificate: wildcard.testdomain.org URL: https://:443/Reports_SQL2008 <<<< automatically generated.(Note that the "Add a Report Manager SSL Binding" section doesn't have a field to specific a host header.) When I click ok, I get the following output under the URLs section: http://COLO-TEST1:80/Reports_SQL2008 http://test1.testdomain.org:80/Reports_SQL2008 https://+:443/Reports_SQL2008From an client on the network, I can successfully navigate to http://COLO-TEST1:80/Reports_SQL2008 and view the Report Manager fine. From an external client, I can successfully navigate to http://test1.testdomain.org/Reports_SQL2008 and view the Report Manager fine. Neither internal or external clients can navigate to https://COLO-TEST1/Reports_SQL2008 or https://test1.testdomain.org/Reports_SQL2008 , respectively. Here are the URL Reservations from my rsreportserver.config file: <URLReservations> <Application> <Name>ReportServerWebService</Name> <VirtualDirectory>ReportServer_SQL2008</VirtualDirectory> <URLs> <URL> <UrlString>http://+:80</UrlString> <AccountSid>S-1-5-21-873839729-4129783965-1078289997-3644</AccountSid> <AccountName>TESTDOMAINservice_sql_ssrs</AccountName> </URL> </URLs> </Application> <Application> <Name>ReportManager</Name> <VirtualDirectory>Reports_SQL2008</VirtualDirectory> <URLs> <URL> <UrlString>http://+:80</UrlString> <AccountSid>S-1-5-21-873839729-4129783965-1078289997-3644</AccountSid> <AccountName>TESTDOMAINservice_sql_ssrs</AccountName> </URL> <URL> <UrlString>https://+:443</UrlString> <AccountSid>S-1-5-21-873839729-4129783965-1078289997-3644</AccountSid> <AccountName>TESTDOMAINservice_sql_ssrs</AccountName> </URL> <URL> <UrlString>http://test1.testdomain.org:80</UrlString> <AccountSid>S-1-5-21-873839729-4129783965-1078289997-3644</AccountSid> <AccountName>TESTDOMAINservice_sql_ssrs</AccountName> </URL> </URLs> </Application> </URLReservations> Does anyone have any ideas of what I could try next?
Hi All, I have the same issue with SSRS 2008 and a wildcard certificate. Did you find a solution? Andrew
Edited for SSRS 2008 with SSL and Friendly URLs Make sure you have a valid certificate installed on the server Open the SSRS Configuration Tool to the Web Service URL page and choose your certificate with port Click Advanced button Add All IPv4, your port and your certificate name Do the same on your Report Manager URL tab Advanced window Restart your SSRS service Test your reportserver address an then copy it Save your current rsreportserver.config file and edit the file by pasting the reportserver address in the <UI> section like this: </Service> <UI> <ReportServerUrl>https://friendlyName.xxx.com/reportserver</ReportServerUrl> <PageCountMode>Estimate</PageCountMode> </UI> You should restart your service. But after that, I was able to access multiple friendly URLs pointing to that server going to both virtuals. MS Support helped me with this. Thanks!