I have a Drupal installation that operates a bunch of domains out of one code base using the Domain Module. How do I set up this module to allow for single sign-on between these sites? If I install the module I get an error saying the client and the controller may not be installed at the same time?!?!

Comments

ayesh’s picture

ayesh commented

Yes that's correct. In my installation(I'm not the maintainer), I setup a separate site just for users and used domain-access-enabled site as a child site. It worked fine.

gateone’s picture

gateone commented
Category: bug » feature
Priority: Normal » Major

Well... sigh. While this might generally be an option, I will end up again with TWO Drupal installations to be maintained. The customer explicitly however did not want that to happen. Also, we do run into problems with co-published content throughout all sights that the Domain module currently offers. It would not work so easily at all for that second, separate installation anymore.

The previous module Shared Sign-on by the way was perfectly capable of handling this scenario: ONE installation, multiple sites (e.g. through Domain module) and signon worked flawlessly until Shared Sign-on was pulled from Drupal.org in favor of this module. Of course, this previous module was far less sophisticated than Single Sign-On of course.

In one word: this basically is a feature missing in this module, so I will mark this issue a feature request which I believe many of us could really need! Single Sign-On Module should really play with a single code base Drupal installation using the Domain module (or any other way of doing the same thing out of one code base).

chriz001’s picture

chriz001 commented

Subscribe - I would also love to see this feature implemented, however im using drupal 7

ayesh’s picture

ayesh commented

Shared Sign on is still available to download at drupalmodules.com. But DO NOT use that module. There is a good reason to unpublish all releases. If you are good with module development, you can take that module as an example and modify/create-from-scratch module/a-module.

If I can remember correctly, that module's problem is remote access regardless of DA-registered domain. I can't remember. So wrapping the access to DA will do the job.

Ken, the awesome DA module developer has documented DA's API.