Use fully-qualified domain names instead of subdomains?

This would be great. The sites we are working would actually be using the onesite.com, twosite.com structure instead of one.site.com, two.site.com. More flexibility is always good.

Wouldn't just changing the $cookie_domain setting in the settings.php file work?

Here is how I set up apache to strike a balance fully qualified domains and subdomains. With this set up end-users will only ever see and use the fully qualified domains however all management editing has to be done via the subdomains.

I have following sites (names changed to protect the innocent) set up in the domain access module.

audi.allcars.com
vw.allcars.com
honda.allcars.com

I edited settings.php so that my cookie domain is allcars.com. This allows me to be logged in across all sites.

My main vhost config looks like this:

<VirtualHost *>
  DocumentRoot /var/www/allcars
  ServerName allcars.com
  ServerAlias audi.allcars.com vw.allcars.com honda.allcars.com
</VirtualHost>

Then I set up a vhost for each of my fully qualified domains so that they proxy their respective subdomains. The ProxyPassReverse directive is needed if you want forms that do redirects (like the search form) to work.

<VirtualHost *>
  ServerName www.audi.com
  ProxyPass / http://audi.allcars.com/
  ProxyPassReverse / http://audi.allcars.com/
</VirtualHost>

<VirtualHost *>
  ServerName www.vw.com
  ProxyPass / http://vw.allcars.com/
  ProxyPassReverse  / http://vw.allcars.com/
</VirtualHost>

<VirtualHost *>
  ServerName www.honda.com
  ProxyPass / http://honda.allcars.com/
  ProxyPassReverse  / http://honda.allcars.com/
</VirtualHost>

P.S. There seems to be some kind of url filter running which messes up the vhost listing.

If you look at the comment I posted you will notice that the urls have been automatically hyperlinked (I entered them as plain text). Unfortunately it seems that whatever was used to do the linking got a little overzealous and linked some of the vhost tags as well.

Marc

I've just installed Single Sigon with Domain Access and it seems to work cross-domain without any modification. (Note: leave $cookie_domain unset).

I was surprised it actually was pretty simple.

1. Domain Access was already configured and working. (Basic setup. Default domain + 3 additional subdomains (like tv.domain.com, tv-a.domain.com, tv-b.domain.com,...) and 1 different domain tv.domain2.com. No prefix for any table. Clean-urls actived on drupal).
2. Untar SSO.
3. Go to admin > build > modules > modules and enable SSO
4. Go to admin > settings > singlesignon and enter the url of the default domain.
5. Comment $cookie_domain line on settgins.php

I've found only 1 issue so far. SSO only works if I make login in any non-default (ID != 0) domain. Login in the default (ID==0) domain does't propagate the session to the rest of the domains.

Hmm. It seems logical to me, then, that the bug is in the singlesignon module (so maybe it should be reassigned there).

But unfortunately the maintainer for that appears to have only made 7 comments in the last year. There are also 5 things claiming to be patches sitting in its queue. I also have an additional (one-line) patch that makes Single sign-on work more happily with Google and other bots.

Does this seem relevant?

http://drupal.org/node/132015

#132015: I often get "page not found" contains a fix for this bug. It would be really nice if Domain Access would have these paths already added upon installation.

Thanks, sun. I was just coming here to ask about this :).

Yes, a hook in SSO would be great.

Since the original topic of this issue has already been fixed, let's continue this discussion over at #256007: Single Sign-on and SEO - already including another patch for Domain Access.

Setting back original status.