This is kind of a backwards request... We have a SSRS 2012 server using a valid GoDaddy SSL certificate. Everything works fine, and now we want to publish that website through our Imperva reverse proxy. The weird thing is that Imperva wants to access that web page by IP address, not DNS name. And it needs to do it using SSL. Meaning it wants to access the site like this:https://192.168.0.1/Reports instead of like this: https://ssrs.mydomain.com/Reports.
True, accessing an SSL enabled website by IP address will create certificate errors, since the URL won't match the certificate. But apparently that's what Imperva wants. The problem is, SSRS (understandably) won't respond on 443 when being accessed using an IP address. I see how I can easily make the site respond by IP address when accessing the site without SSL, but I need both. SSLand it needs to respond by IP. Ever since Microsoft integrated the IIS engine into SQL, we've lost the IIS MMC that might help me force the website to respond the way I need it to. So does anyone know any other way of doing it?