Hello,
I have a multiportal DNN installation with all primary portals having their own domain name, and  where one of these domains is using an SSL certificate. Such certificate is of course installed in IIS (now IIS 6).

I now need to add SSL certificates to other portals in this host, but this is not possible - we need an unique ip address for each SSL cert afaik.
I'm now wondering whether multi-domain ssl certificates (such as https://www.rapidsslonline.com/true-b... ) could help: if I understand right a multi-domain certificate would be released for different hosts (say www.domain.com and www.anotherdomain.it), so I should be able to use it on my multi-portal DNN host.

Am I right? Did anybody experience multi-domain ssl certificates with DNN?
Any help greatly appreciated, thank you.

Regards,

al.

If you have running many different domain names on your portal instance, you should use a SAN Certificate where all used Domains should be listed in.  eg.:

• www.domainname.com
• www.domain.com
• www.domainname.net
• www.domain.net

If you using one domain name with some subdomains you could use a wildcard Certificate. eg.:

• *.domainname.com

If you running own portal instances eg. with an objectQualifier on one database or with a own database you could install own Certificate per instance.

You are right.  An UCC is also an SAN Certificate, but it is a special certificate that is approved for Unified Communication applications e.g. Lync, Exchange.  An UCC certificate would also be worked.

If you need to add a new domain if you have running a SAN Certificate, you have to re-new your certificate with added the new domain to the alternate domain list.