View Single Post
  #5  
Old 6th March 2007, 21:27
Sheridan Sheridan is offline
Junior Member
 
Join Date: Jun 2006
Posts: 26
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by martinfst
I think you ask two questions.
1. One Cert for multiple domains: this is not possible because of the way ssl is working. SSL Certs work for one domain and one IP. There is a special case for wildcard certs, which will allow multiple system hostnames to authenticate with the same Cert, but that's the only exception.
I think i have to give you an example on what i mean with one cert for multiple domains.

Let's think about a server that has the following hostname "server1.mydomain.com". server1.mydomain.com also exists as a valid dns A-record.
So you now create a cert for "server1.mydomain.com". Then you have to configure apache to use name-based virtual hosts for <yourip>:443 like in the following example:


Code:
<IfModule mod_ssl.c>
NameVirtualHost <ip-address>:443

<VirtualHost <ip-address>:443>
        ServerName www.domain1.com:443
        ServerAdmin admin@domain1.com
        DocumentRoot /var/www/web1/web
        ServerAlias domain1.com
        .....
</VirtualHost>

<VirtualHost <ip-address>:443>
        ServerName www.domain2.com:443
        ServerAdmin admin@domain2.com
        DocumentRoot /var/www/web2/web
        ServerAlias domain2.com
        .....
</VirtualHost>

.....
</IfModule>
Maybe calling that "one cert for multiple domains" has been confusing, but the above configuration is definitely working and valid. Plesk, for example, supports that kind of apache configuration. I think it's the default behaviour until you upload or create your own cert.


greets
Sheridan
Reply With Quote