The title says it all... unfortunately, I haven't found a solution for this on Drupal 7. I was able to use the SSO module on Drupal 6, but it is not being actively maintained. Neither is the multisite_login module.... both Drupal 6.

Anyone have any ideas? Suggestions? This is looking like a pretty big road block for my Drupal 7 install.

Thanks!

Comments

dalegrebey’s picture

Just to clarify, I am not referring to sub-domains, but domain1.com, domain2.com, domain3.com ...etc

socialtalker’s picture

of course i could use the facebook, openid, twitter option, but i thing not having able to offer visitors/customers a unique id across a network of sites is too me a big loss of identity and privacy. at least i hope there is some kind of "recipe"
update:
did you look at domain access? its been ported to 7, i am going to try that
http://drupal.org/project/domain

BrentRoger’s picture

I'll admit I'm not that versed in multiple site configurations for any version of Drupal but having read the settings file I get the impression using a set of shared tables (including) "users" would suffice.

* You can optionally set prefixes for some or all database table names
* by using the 'prefix' setting. If a prefix is specified, the table
* name will be prepended with its value. Be sure to use valid database
* characters only, usually alphanumeric and underscore. If no prefixes
* are desired, leave it as an empty string ''.
*
* To have all database names prefixed, set 'prefix' as a string:
* @code
* 'prefix' => 'main_',
* @endcode
* To provide prefixes for specific tables, set 'prefix' as an array.
* The array's keys are the table names and the values are the prefixes.
* The 'default' element is mandatory and holds the prefix for any tables
* not specified elsewhere in the array. Example:
* @code
* 'prefix' => array(
* 'default' => 'main_',
* 'users' => 'shared_',
* 'sessions' => 'shared_',
* 'role' => 'shared_',
* 'authmap' => 'shared_',
* ),

Am I oversimplifying things? If so, it's by no means intentional.

I'm trying to do something similar but I think I'll start a new thread for it. In a nutshell I want to use the same content for two different URLs with two different themes, one for my www site and one for my mobile devices site. I found a module for v6 that I'm pretty sure accomplishes this (Sites) but it's not ported to 7. I was hoping something along these lines (considering how prevalent mobile browsing is these days) would have been built into the core but it doesn't appear to be the case.

dalegrebey’s picture

Frankly, I'm not too sure if table prefixing would or wouldn't work. Thanks for the direction, I'll have to look into this and play around with it for awhile to get a better sense.

As far as mobile browsing goes... you're using 2 sites? Correct me if I'm wrong, but wouldn't it be better to use one site, detect whether it's a mobile phone user agent or not and than include a separate stylesheet?

<link rel="stylesheet" href="mobile.css" type="text/css" media="handheld" />
Yaron Tal’s picture

http://drupal.org/project/wurfl
For detecting if it is a mobile device and from that page:
"Device groups is a concept introduced by the Mobile Tools module in order to switch to different themes depending on the device. "

Shared tables won't work. I am now looking into the sso module:
http://drupal.org/project/sso I am thinking about combining it with the domain access module.

dalegrebey’s picture

My understanding about table prefixing, as it goes, is that yes it will allow me to share database users, etc, but that they would still have to relog between the domains. hrrm.

lafe0002’s picture

You could try to use CAS

R.J. Steinert’s picture

That works, but setting up another server to run Java seems kind of overkill if you only want 2 or 3 sites to share user accounts and authenticate once across domains. I might change my mind if someone out there is doing CAS as a service. My clients wouldn't mind a small fee to keep user accounts synced across sites and have a single sign on.

http://drupal.org/project/cas

Be well,
R.J. Steinert III
RjSteinert.com

"Happiness is the process not the place."
-Diener

R.J. Steinert’s picture

simplesamlphp_auth looks like a good option for a single sign on. It utilizes the PHP library SAML.

It makes it possible for Drupal to communicate with SAML or Shibboleth identity providers (IdP) for authenticating users. The resulting Drupal site can effectively act as a SAML or Shibboleth service provider (SP).

http://drupal.org/project/simplesamlphp_auth
installation -> http://drupalcode.org/project/simplesamlphp_auth.git/blob/refs/heads/7.x...

Be well,
R.J. Steinert III
RjSteinert.com

"Happiness is the process not the place."
-Diener