We're hosting sites for several clients and ideally would like to use Domain Access. There will be a considerable amount of shared content so it would certainly make things easy. Some of the content must use SSL. Additionally, there will be multiple domains (e.g. company.com, example.com, another.com).
Hosting is at Media Temple on a DV server. Obviously all of the domains would be using a shared IP address.
I'm trying to figure out how I can make this work on the SSL side. I don't see how a standard certificate can work since it requires one domain per IP. I don't think Wildcard SSLs work in this case since there are different domains, not just subdomains. Perhaps something like GeoTrust Multi-Domain SSL would work. If necessary I can have the SSL content on a subdomain so www.example.com is non-SSL and secure.example.com is SSL.
Another question is about choosing the base URL in Domain Access (I believe that's the option - http:// or https://). Does that mean the entire domain needs to be EITHER http:// or https://? We can't use SSL for some but not others?
Thanks.
Comments
Comment #1
agentrickardThe scheme is only used when Domain Access rewrites node links to absolute URLs. Otherwise, DA inherits $base_url as set by the inbound request.
I don't know about the other issues. We're running two separate domains (e.g. http://example.com and https://secureexample.com) on one IP and a single cert with no known issues. But the content on the SSL site is essentially walled off from the other site and only used for transactions.
There are folks running Ubercart and DA who might chime in here.
Comment #2
agentrickardIs the problem that you need more than one domain running SSL?
A MT dv can have multiple IPs that point to different domains. And you can resolve them to one drupal install.
Comment #3
Lloyd commentedWe'll have, for instance, three different domains (company1.com, company2.com, company3.com). All will be using the same Drupal install with Domain Access. Certain pages of the site needs to be on SSL. My limited understanding of SSL leads me to believe that I need a separate SSL cert (or one cert that can handle multiple domains) for each domain. I can't install just one cert for primarydomain.com and have the other domains use it, right? And I believe MT requires (which is probably a limitation of a standard SSL cert) that each domain requiring an SSL cert have a dedicated IP address.
So the question is, I guess, how do you provide an SSL cert for multiple domains using one Drupal install with Domain Access? I can't see how we can setup each domain on its own IP and use one Drupal install and share content with Domain Access. If that's possible, great. I just don't see how it can be done.
Comment #4
agentrickardAs long as those IPs point the web server to the same Drupal root, you should be fine. E.g.
Or
Which might be done with VHosts. I don't know. I am not a sysadmin.
Comment #5
Lloyd commentedSo in your example, we'd setup an individual domain on a separate IP for each. And then point www.* over to the drupal installation. And despite the content being on a server different than the hosted IP, the SSL should work?
I'll give that a shot.
Comment #6
agentrickardNo. They all have to be on the same server.
Comment #7
agentrickardComment #8
jday commentedI was able to set up multiple ubercart stores with domain access, each with its own domain (store1.com, store2.com, store3.com). The site was hosted on a goddady economy server, then we bought a 5 domain UCC certificate and set it up through the godaddy interface. Works perfectly.
I would love to do the same with a different set of sites hosted on slicehost but I can't find any write ups on how to configure/install the UCC on a linux server.
Comment #9
Lloyd commentedI'm revisiting this issue. Let's say I have a drupal installation using www.abc.com on a server using ip address 1.1.1.1 and domain access installed. I'd like a different domain www.xyz.com to be part of the domain access installation. Both domains need (their own) SSL certificates.
Would it be possible to install the second domain using a different ip address (2.2.2.2), point that domain over to the installation with domain access, and then use vhosts or something else to make everything work correctly?
Comment #10
dqd