Forum Moderators: coopster
I have 4 domains. 1 of them is the single sign on domain (where the users profile database is) and the other 3 domains are vertical services.
single-sign-on-domain.com
vertical-service-1.com
vertical-service-2.com
vertical-service-3.com
Once the user registers itself on single-sign-on-domain.com he has automatically access to the 3 vertical services (all domains are on the same server so there is no problem regarding DB usage).
Of course, to avoid repeatedly sign-ins, i want the user to just sign in on the single sign on domain once, and then have the session vars do the rest of the job for the other domains.
Is it posible? If so, how? Am i applying a viable paradigm here? Any suggestions? thanks.
the easiest way to do it would be to put the info into an MySQL table or something similar, and give each site access to the same table.
regarding: "the easiest way to do it would be to put the info into an MySQL table or something similar, and give each site access to the same table."
actually that has been already implemented ;)
the actual problem comes when i try to handle the SESSION data. Despite all domains are on the same server, i cannot modify it's php.ini session.save_path variable, which means that each domain is configured to place the SESSION data in their own directory folders.
Can that variable be handled with htaccess?
something like this...
<?php
session_save_path("/path/to/whatever/");
session_start();blah blah blah
?>
[EDIT... obviously you will have to place the path outside of the root, otherwise each site would still be looking inside their own site structure.]
Warning: session_save_path() [function.session-save-path]: open_basedir restriction in effect. File(/home/singlesignon/public_html/temp) is not within the allowed path(s):
that message comes when trying to save session data from within www.example.com ... any other suggestions?
[edited by: coopster at 9:25 pm (utc) on July 28, 2007]
[edit reason] generalized domain [/edit]
This tutorial from Zend on custom session handling [zend.com] will get your started down the right path but it won't be the end-all. Check out this article on <snip>
[edited by: eelixduppy at 5:19 am (utc) on July 27, 2007]
[edit reason] removed url as per charter [/edit]