Posted by Flying Drupalist on December 6, 2008 at 11:23pm
Hi, all the guides I've read suggested that for sharing users you need to share the sessions table. But that means that when a user is logged in on one site, all other site tracks that user as logged in. To make the who's logged in block work, would it be wiser to split up the session tables?
Is there any reason why I shouldn't? Thanks.
Comments
not exactly....
When you login to sessions are going the session from actually using domain - when you login from another domain the cookie set will be different. You can not login once and then change domain. You must login yourself another time. This table is "shareable".
Hi, sorry for being unclear.
Hi, sorry for being unclear. My problem was that when a user is logged in on one site, the who's online block will show him logged in on ALL sites if sessions is shared. Would unsharing it fix this problem?
Thanks.
I think...
I think - yes. It would help in my opinion.
Having a separate session
Having a separate session table for each of the sites will resolve the issue.
Netlink Technologies Ltd
http://shyamala-drupal.blogspot.com/
Shyamala
Unimity Solutions
Alright thank you. :)
Alright thank you. :)
You will loose one advantage
You will loose one advantage of sharing the session table though. ie. users will have to login on each site they go to (which may or many not be what you want for usability). I share the session across multiple subdomains and the biggest advantage is it gives single sign-on and log off functionaliy across all network sites. Because of portals like yahoos and google provide this, more and more uses expect to have single sign on.