I see that voting for sessions is coming up fast (on 16th Feb). I actually submitted my two solo talks early, at the request of the organizers.
And, for the truly geeky, many of the features in Domain Access inspired Node Access changes in Drupal 7.
So remember to vote early and vote often.
Contact me for availability.
Comments
If we have XML sitemap +
February 11, 2010 by Dave Reid (not verified), 1 year 51 weeks ago
Comment: 283
If we have XML sitemap + Domain access working by then, let's have a drink. If not, let's have a hackathon. :)
NZ parliament (aka beehive) on Drupal too
February 11, 2010 by Bevan (not verified), 1 year 51 weeks ago
Comment: 284
Huh! I didn't know there was more than one beehive running Drupal! http://beehive.govt.nz/
I'm still aiming for my
February 11, 2010 by nonsie (not verified), 1 year 51 weeks ago
Comment: 285
I'm still aiming for my internal deadline for XML sitemap and Domain Access. We can always drink and make it better in SF
Question about Domain Access module.
February 13, 2010 by KM (not verified), 1 year 51 weeks ago
Comment: 290
Does the Domain Access module accomplish the following (in the case of multiple sites with unrelated domain names, but housed on the same server)?
1. All sites share a single user id/password database.
2. Allow visitors to any of the sites to login once and be able to roam freely across the multiple domains as a logged in user to all.
I am looking for something that can do that and was reading about your module. But I just wanted to confirm it with you that this can be accomplished. If your module does not do this, is there another one you know of that will?
Thanks for any info you can provide.
Answers
February 13, 2010 by agentrickard, 1 year 51 weeks ago
Comment: 291
Not without an additional single-sign on solution, like OpenID or the Single SignOn module. If you share a top-level domain, then you can simply share cookies.
Even though you would share a single database {users} table, the login auth system needs to be able to set / read cookies.
But with those additional modules and your's...
February 13, 2010 by KM (not verified), 1 year 51 weeks ago
Comment: 292
Can I then do exactly what I'm looking to do?
Having the multiple sites set up as sub-domains under one top-level domain MIGHT be an option, but it is more likely that it will have to be across multiple domains.
I first found the info about Single SignOn, but then I read this article:
http://drupal.org/node/291373
and that made me worry that things might get complicated. So I kept looking. Then I saw your module with following in the description:
The Domain Access project is a suite of modules that provide tools for running a group of affiliated sites from one Drupal installation and a single shared database. The module allows you to share users, content, and configurations across a group of sites such as:
* example.com
* one.example.com
* two.example.com
* my.example.com
* thisexample.com <-- can use any domain string
* example.com:3000 <-- treats non-standard ports as unique
and that led me to wanting to confirm with you that the fifth one I've put in bold above means any domain at all including ones not tied in any other way to the initial site.
Do I understand it correctly then that your module on its own will allow for a shared user id/password database with other sites, but users will have to login whenever they switch to a different domain, since the cookie will only apply to the initial domain. But to avoid having to force users to log in again if they go to one of the other sites, then I'd need Single SignOn or OpenID, and that will work. Is that right?
Thanks for the clarification.
Yes
February 13, 2010 by agentrickard, 1 year 51 weeks ago
Comment: 293
Yes, you understand correctly. This is a security aspect of the cookie standard.
Very cool. Glad it is doable.
February 13, 2010 by KM (not verified), 1 year 51 weeks ago
Comment: 294
Thanks for the info.
Post new comment