share a private SSL for multiple domains

[mydanilo]

I read in different places about this possibilities, but I still have questions.

I intend, on a shared hosting account, to host multiple domains. First domain will be my main domain and others will be added as ad on domains. The private SSL will be issued for the main domain. A dedicated ip address will be used for the main domain. Main domain and add on domains will have Zen installed.

Q:
Can I use the same private SSL to protect check out for my add on domains as well? Does this only make sense to do (sharing the SSL) for sub domains or is this also ok for add on domains? How would this sharing of a private SSL be implemented in details? Are there any security concerns for sharing a private SSL?

I guess a primer on this issue would be appreciated from somebody solid on this topic. Thank you for anybody offering insight.

[Merlinpa1969]

the extra domain names will be
https://www.YOURMAINDOMAIN.com/addon domain name folder/

[mydanilo]

That's it? How about pop up warnings? Is this throwing any warnings?
No dedicated IP needed for the ad on domains?

Does this require to install the ssl in a special way?

I thought other posts in this matter were much more elaborate, in fact I could not quiet get it how this should work.

Merlin, you are a master in fast responses. Thank you.

[Merlinpa1969]

all an addon domain name is is a folder and a redirect,

www.domainb.com is really a subdomain of
www.domaina.com

so to ssl it it would be https://www.domaina.com/domainb/

no this wont cause any errors, and no the cert dosnt have to be installed any certain way.

we have several that are done this way

[mydanilo]

OK, I think I understand now. I will put this in my own words and post this as an example. Please let me know if this makes sense.

Here is my case: All my domains and addon domains are owned by the parent company. We run multiple stores. Charges to the customers credit cards are always made through the parent company. I would like to host them in one shared hosting account. I would like to buy only one SSL certificate.

Implementation Scenario:

Main Domain: parentcompany.com

Addon Domain: store1.com
Addon Domain: store2.com

Secure Path: https://www.parentcompany.com/store1
Secure Path: https://www.parentcompany.com/store2

So far so good.
Now something little extra, one of the Zen Carts is currently running in a sub directory of store1. www.store1.com/zencart

I guess the secure path for zencart would then be:
https://www.parentcompany.com/store1/zencart

Does this all sound correct?

Other thoughts:
I think this would not look too fishy to the customers as only the parentcompay is added to the path for secure pages. I think it would look fishy if the path would be something like:

https://www.noideawhatthisis.com/store1 or
https://www.otherwiseunrelated.com/store2

I think some people actually do look at what is displayed in the address bar.
:)

[Chuckl]

Danilo,
If you wanted to set up individual domains for each store, it is possible, using Vhosts and a single IP, to generate a certificate that includes a Common Name for the server and SubjAltNames for the domains.
This works fine, but requires you to generate a new certificate every time you add a domain. If you can largely define them all up front, thats not a problem, but probably not ideal for a constantly changing service provider environment.
Translating into english, you can have a server called 'server3.parentcompany.com' running domains 'www.store1.com' 'www.store2.com' 'www.store3.com' etc on 1 IP address.

Chuck

[mydanilo]

..and this would work on a shared hosting account?

If I know all the domain names I want to use upfront, then I could add them at the point were we generate the certificate, and all domains could use their own https path?

Like:

https://www.store1.com
https://www.store2.com
https://www.store3.com
https://www.store4.com
?

All with one simple normal certificate? Sounds great! I wonder if my host knows how to pull this one off.

[Chuckl]

No idea about your host and their capabilities or willingness... I suspect the answer will be no.
I have tried this and use it as my service provider wants ridiculuos amounts of money for additional IP addresses, but it's my server, so the hosting staff are very helpful.

What you would need to establish on the Apache webserver side is as follows:

1. Are they using virtual hosting? typically the answer is yes.
2. Can they set UseCanonicaName on in the Vhosts file for your sites?
3. Will they set up the vhosts config in Apache so that all your secure sites have an entry with the same IP address?
4. There will probably be a bit of work installing the certificate.

The certificate signing request is fairly easy to generate, just a slight mod of the standard script. If you're interested in pursuing it, I can dig out some references for you

Chuck

[mydanilo]

Thank you Chuckl,

I think I will go with Merlinpa's suggestion for now. I suspect it would be too much asked for my host.

[mydanilo]

I now got this working with a private SSL.

My only problem is now admin login. I log in with SSL path and get inside admin. If I choose any other menu or section of the admin, it bounces me back to the https login page. What is going on? I can't figure it out.

Here is my config:

define('HTTP_SERVER', 'http://www.perfectpairweddingfavors.com');
define('HTTPS_SERVER', 'https://www.duda-inc.com/perfectpairweddingfavors');
define('HTTP_CATALOG_SERVER', 'http://www.perfectpairweddingfavors.com');
define('HTTPS_CATALOG_SERVER', 'https://www.duda-inc.com/perfectpairweddingfavors');

// Use secure webserver for catalog module and/or admin areas?
define('ENABLE_SSL_CATALOG', 'true');
define('ENABLE_SSL_ADMIN', 'true');

// NOTE: be sure to leave the trailing '/' at the end of these lines if you make changes!
// * DIR_WS_* = Webserver directories (virtual/URL)
// these paths are relative to top of your webspace ... (ie: under the public_html or httpdocs folder)
define('DIR_WS_ADMIN', '/admin/');
define('DIR_WS_CATALOG', '/');
define('DIR_WS_HTTPS_ADMIN', '/admin/');
define('DIR_WS_HTTPS_CATALOG', '/');

define('DIR_WS_IMAGES', 'images/');
define('DIR_WS_ICONS', DIR_WS_IMAGES . 'icons/');
define('DIR_WS_CATALOG_IMAGES', HTTP_CATALOG_SERVER . DIR_WS_CATALOG . 'images/');
define('DIR_WS_CATALOG_TEMPLATE', HTTP_CATALOG_SERVER . DIR_WS_CATALOG . 'includes/templates/');
define('DIR_WS_INCLUDES', 'includes/');
define('DIR_WS_BOXES', DIR_WS_INCLUDES . 'boxes/');
define('DIR_WS_FUNCTIONS', DIR_WS_INCLUDES . 'functions/');
define('DIR_WS_CLASSES', DIR_WS_INCLUDES . 'classes/');
define('DIR_WS_MODULES', DIR_WS_INCLUDES . 'modules/');
define('DIR_WS_LANGUAGES', DIR_WS_INCLUDES . 'languages/');
define('DIR_WS_CATALOG_LANGUAGES', HTTP_CATALOG_SERVER . DIR_WS_CATALOG . 'includes/languages/');

Any idea?