5

The background: We (currently) have 2000 domain names pointed at a single IP. Drupal inherently has the ability to use multisite, but for our particular Drupal 7 install we use a module named Domain Access to delegate sites. The gist is though that Domain Access will not allow cross site logins, but yeah, we would like our editors to log in once, and have access to all sites.

The question: Has anyone made any headway with coming up with a single sign on solution with Domain access to date for Drupal 7? I've been looking closely at two old modules, one no longer maintained (SSO for D6) and one still maintained (CAS). I'm worried about using CAS I am not sure if it will work the way I intend it since Domain Access seems to change quite a bit of Drupal(ly) stuff.

We could potentially use facebook, openid, twitter option, but i thing not having able to offer visitors or customers a unique id across a network of sites is too me a big loss of identity and privacy.

Are there any solutions that are known to date, or information on what to start looking into? Has anyone in the Drupal community managed to make a solution that I have not been able to find? The only possiblitiy that I've found was this thread on Domain Access SSO but am uncertain to what version it pertains to (Drupal. DA, SSO or otherwise). I tried contacting the author multiple times but never received a response. It looks like the "Solution" was to create a master table set with users and permissions, then share those across the domains. Unfortunetly (again) SSO on Drupal 7 is not an option.

Any opinions out there on the who what or why would be greatly appreciated, I honestly just need a start point to get the ball rolling. Thanks everyone

Improve this question
4
  • 2
    Just to confirm, by SSO you mean that if a user logs into domain1.com, they would already be logged into domain2.com when Domain Access is in play? SSO can mean different things to different people, and this is a good question. Making sure we are all on the same page is necessary for good answers here.
    – mpdonadio ♦
    Dec 8, 2011 at 2:54
  • Yes once they log into domain1 they would essentially be logged in to all our TDLs (Top Level Domains) like domain2.com domain3.com etcetra. My use of SSO is I believe the correct use. Where user authorization data is passed from the primary login point to all other TDLs in our control. Please correct me if I am smudging the term though.
    – ehime
    Dec 8, 2011 at 20:41
  • Yeah, that is the correct term. I have heard the term used more loosely to refer to multiple systems using centralized credentials (eg, OpenID, AD, LDAP) but requiring users to log into each.
    – mpdonadio ♦
    Dec 9, 2011 at 14:08
  • I know that authentication is strongly used in the inc/session.inc file. This is also where sso works on. Now SSO is not the right approach for domain acces in my eyes, because you are working on a single database. I am also looking for a solution to this.
    – Nealv
    Jan 3, 2012 at 10:05

1 Answer 1

Reset to default
2

See: Comparison of Single Sign On (SSO) Modules

Bakery supports SSO for sites with the same domain (site1.example.com, site2.example.com). Have not tried CAS as you noted above it is an option. You could also use an oauth server to authenticate across domains.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.