We are looking to set up a cloud solution for one of our systems, but we need multiple TLD SSL's
- We are only allowed 5 public IP's
- Can't use UCC/Wildcard Certs since each client has own cert and some have different types of certs
I came up with the idea of setting up cloud load balancers for each client requiring SSL, and point the load balancer to our primary web server, on alternative ports...
Client1LoadBalancer -> webserver:444
Client2LoadBalancer -> webserver:445
Client3LoadBalancer -> webserver:446
. . .
ClientNLoadBalancer -> webserver:N
Are there any other approaches or ideas for this to work other than the cloud load balancing approach?
Besides using IPs in the cloud, there is one other option I can think of Apache can do SNI. Acording to that link, IE6 does not support SNI ( for when it was written ).
It looks like the solution may very well be in Server 8, and specifically IIS8, as it supports SNI (Server Name Indication). "IIS 8.0 supports Server Name Indication (SNI), which has extended TLS to include the virtual domain name to be passed from the client at the time of "SSL Hello". This effectively allows IIS 8.0 to enable "hostname binding" for SSL sites, which eliminates the need for having a dedicated IPv4 address per SSL site."
http://blogs.iis.net/wonyoo/archive/2012/03/01/iis-8-0-platform-features-for-web-hosters-and-service-providers.aspx