Is there a way I can have multiple ssl certificates point to a single inputendpoint in a service definition? For example, lets say I have two url’s.
service.foo.net/Service.svc
service.doo.net/Service.svc
I want both of these addresses to resolve to my windows azure service, but I’m not sure how to configure this in the service definition.
<Certificates>
<Certificate name="service.foo.net" storeLocation="LocalMachine" storeName="My" />
<Certificate name="service.doo.net" storeLocation="LocalMachine" storeName="My" />
</Certificates>
<Endpoints>
<InputEndpoint name="HttpsIn" protocol="https" port="443" certificate="service.foo.net" />
</Endpoints>
According to this MSDN article, each input endpoint must have a unique port. Is there any way to specify more than once certificate for this endpoint?
Unfortunately this is not possible. Azure is re-exposing an SSL limitation. The SSL limitation is interesting, and the reason you can’t use v-hosts over SSL. Lets walk through an example:
Since the server needs to present a certificate before you tell it the host name you want to talk to, the server can’t know which certificate to use if multiple are present, thus you can only have a single cert.