Session cookies and multiple sites
Posted: Thu Aug 23, 2007 12:45 pm
Hello,
I have two sites, lets call them siteA.com and siteB.com. SiteA.com incorperates user posting from siteB.com (a blog site). On siteA.com, you can administer your blogs, write new blogs and they will post on siteB.com. The purpose of this is to split the users information from the actual site. SiteA.com has all the logic for authentication built into it. If you go to siteB.com, you can login to use your blogs there as well, but this is my question or problem.
I'm trying to make it that once you log into siteA.com, if you go to siteB.com, you are already logged in (logout vice versa). SiteA.com is based on a session cookie. SiteB.com has access to that session information sorted in a common database, but can't associate the cookie in the database with the user entering siteB.com. Is there anyway, once the user goes to siteB.com to understand the session cookie written in the DB and write that cookie out for it's domain without the users actually authenticating?
I know all of this siteA and siteB stuff sounds confusing, but I'm trying to be as clear as I can be. If anyone could explain how they would approach this problem, I would appreciate it.
-Phibertek
I have two sites, lets call them siteA.com and siteB.com. SiteA.com incorperates user posting from siteB.com (a blog site). On siteA.com, you can administer your blogs, write new blogs and they will post on siteB.com. The purpose of this is to split the users information from the actual site. SiteA.com has all the logic for authentication built into it. If you go to siteB.com, you can login to use your blogs there as well, but this is my question or problem.
I'm trying to make it that once you log into siteA.com, if you go to siteB.com, you are already logged in (logout vice versa). SiteA.com is based on a session cookie. SiteB.com has access to that session information sorted in a common database, but can't associate the cookie in the database with the user entering siteB.com. Is there anyway, once the user goes to siteB.com to understand the session cookie written in the DB and write that cookie out for it's domain without the users actually authenticating?
I know all of this siteA and siteB stuff sounds confusing, but I'm trying to be as clear as I can be. If anyone could explain how they would approach this problem, I would appreciate it.
-Phibertek