I have an ASP.NET application on IIS(Windows Azure) which has many different domains. All domains are working on http. Now, I need to use https. Whether, a single certificate is fine for all of my domains which point a single ASP.NET application on Azure or I need a certificate for each my domain.
migrated from stackoverflow.com May 17 '12 at 11:07
This question came from our site for professional and enthusiast programmers.
The key point is that you can only assign a single certificate per Input Endpoint for Windows Azure service deployment. That said, you must have a single certificate for all the domains you want to serve. The way to achieve that is to use Subject Alternate Name (or SAN) Certificate.
Here is a (non-complete) list of some SAN SSL providers:
UPDATE based on the comments
Yes, however this one certificate will be SAN certificate (please follow that link and read more about SAN Certs) and will have all that domains in its SAN (Subject Alternate Name) property. That certificate is typically more expensive that the regular SSL Certs.
NO. There is no issue. That is the purpose of SAN Certificates. Please follow the provided links and read more about SAN Certificates.
Yes, You can secure a different domains using single server SSL certificate. In order to secure multiple domains using single server certificate, that certificate must SAN SSL, which allows up to 100 multiple domain SSL security on single one.
Below enlisted are the list of the most trusted SAN SSL certificate provider, but at low price:
-> verisign -> rapidsslonline -> digicert