@mukurdhom, Load balancers typically have SSL termination capability, and can have wildcard certs configured directly on them. If your LBs don't have SSL support, you can submit individual certificate requests to a CA (Certificate Authority) for each subdomain/server -- which may add management burden and possibly cost more, in comparison to adding SSL termination support to the LBs. Since your infrastructure already has a load balancer, I'd look into applying an wildcard cert, and call it a day! Not sure what LB product your firm uses, the concept and process outlined below are pretty standard across the board:   http://support.f5.com/kb/en-us... Hope this helps! ~@~ Last edited: 17-Jul-12 11:13 AM

saajha · Jul 17, 2012 11:06 AM

@ Mukurdhom ,           Since your diagram shows domain1 , domain2 etc.. , wild card certificate would not work , however multi-domain ssl certificate would work. Or in another case, you would have to get SSL Cert for individual domain and since they seem to be hosted on the same webservers , you would have to use multiple IPs on the web servers for each website. It's a little more complicated to support different SSL Certificates on the same IP. Thanks Nishant

nishant322 · Jul 19, 2012 1:02 PM

If those are separate domains -- then wildcard cert is indeed not the solution.  My impression, from "There is a single website setup on IIS.." is that there's a single domain (with multiple subdomains) associated with the site. If there's a way to get the client(s) trust self-signed certs, you could establish your own certificate authority, and generate certificates. It's mostly feasible in a proxy'd environment, as you only need to make the proxy trust that cert, and have the trust inherit down to the browsers.    ~@~

saajha · Jul 19, 2012 3:54 PM

 I don't know so much about how it is done through load balancers but you can give a try to the following: 1. Install the certificates to the "Local Computer". 2. Import the certificates to the IIS. 3. Assign www.domain1.com certificate to the www.domain1.com website. 4. Require IIS to have secure connection. If you tell me the OS and IIS version, i might be able to give a more detailed response. The load balancers have a lot of capabilities. This might be also done easily from the load balancer.

jhapaliketo · Jul 19, 2012 6:36 PM