I wrote an ASP.NET MVC application that allows a user to specify their own domain. I have IIS configured to send all requests to the website by default, so I don't need to use host headers. Everything works perfectly. The only problem is SSL.
I know that this question has been asked several times in many forums, but the answers usually contradict or are said in absolute terms (this is impossible). This is not an option for me. I am looking for several options here; I am open to non-traditional :).
I saw some constructive answers that suggest using an ISA server as an SSL proxy. Does anyone know more about this? Or did someone set it up and succeed?
Basically, I want to provide my users with a way to request a CSR from an application, purchase and download an SSL certificate, return to my application and download a certificate issued by an authorized certification company.
I would like to do this without providing separate IP addresses to clients who want to use their own domain and ssl on their site. This is simply because my application is hosted in the Amazon cloud, and they are not keen to provide me with a large block of IP addresses.
My application can be hosted on IIS6 or IIS7, if that matters.
SOLUTION: Thank you for helping these guys. Of course, I did not understand this problem, as now. I think that now my decision will be to create a wildcard certificate and force my clients to use clientname.someshareddomain.com if they want a secure connection. For clients who are just not right with this, I will probably provide another elastic IP address via an api call to amazon web services, create a new website in IIS and point it to the root folder of the application and then programmatically create a CSR from this new site. I just need to develop some kind of deal with Amazon to give me a decent block of IP addresses.
source
share