Hi, I am using multi-site with subdirectories, and I am having trouble getting this module to work.

can the "master" be in a subdirectory, or does it need to be at the root of a domain?
can any of the other servers be subdirectory installs?


#8 sso.patch2.24 KBdavividal
Members fund testing for the Drupal project. Drupal Association Learn more


wdennen’s picture

Version: 6.x-1.x-dev » 6.x-1.3
tttt’s picture

Version: 6.x-1.3 » 5.x-1.3

I'm trying the same thing with no luck. Has anybody got this working for subdirectories?

tttt’s picture

Version: 5.x-1.3 » 6.x-1.3
lelizondo’s picture


lelizondo’s picture

seems like this isn't working when the master site is in a subdirectory, I had to create a subdomain for the subdirectory and it worked. I have something like this:

(that didn't work) but if I create a subdomain like:


it started working great.

digitalpro’s picture

Hi--I'm also having trouble getting shared sign-on to work with my 2 domains both of which are in subdirectories (because they are both new versions of existing sites and the old content is being left in place).

I'm really nervous about ripping them up and starting over to try and "fix" that, especially since one of them has gone live, so I'm wondering if anyone knows if there is some way I can create a new "dummy" domain or some other construct so that shared sign-on can work across these two sites.

I've already built a small module that can validate new users against our forum software (ubbthreads) and create a drupal account and log the user into the current domain (via user_load) so perhaps there is a way that I can log the user in to my other site programmatically at that time?

Thanks for any thoughts!--David Cardinal

digitalpro’s picture

Just a quick update. I moved my master site out of its sub-directory and the module sort of started working. However it still seems confused because my "slave" site is in a sub-directory (nikondigital.org/content) so that when I log in to it it uses the same sub-directory path (/content) as a prefix for it's call to the module in the master site (cardinalphoto.com). So the URL is wrong in that it has an extra /content in it.

It seems like this should be fixable through some type of configuration without using brute force? Thanks for any thoughts.


davividal’s picture

Assigned: Unassigned » davividal
Status: Active » Needs review
2.24 KB

Yes, it does.

But only with a patch. :-)

Can anyone review this patch and give me feedback, please?

I just changed the use of $base_url to $base_root, because when using $base_url you'll get something like http://domain.tld/drupal/drupal/some/thing.

Please, ignore this. Wrong project.

Refer to http://drupal.org/project/sso

davividal’s picture

Assigned: davividal » Unassigned
Status: Needs review » Needs work

Since I patched the wrong plugin, I'm unassigning this issue.