Active
Project:
Single Sign-On (aka SSO or Single Sign On)
Version:
6.x-1.0-rc1
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
26 Jan 2010 at 11:01 UTC
Updated:
18 Aug 2011 at 02:28 UTC
Jump to comment: Most recent file
Comments
Comment #1
Oscar Illada commentedI wonder how popsugar do, if any one have the answer please let me know...
Comment #2
zyxware commentedI think the module is already designed to take the user back to the client site once the login form is submitted. Also the login form is submitted on the client site and not on the controller site. I checked it out on a multisite installation and it looks like on successful login the user is redirected to the home page of the controller site. I checked out the debug log in the singlesignon_controller_associate and $_GET['origin'] seems to be set but the redirection is not happening correctly to the client site.
Comment #3
zyxware commentedOn the site that I had tried to debug, the problem was because of login_destination module which prevented singlesignon_controller_user_form_submit from getting executed as it was redirecting users to the home page of the controller site. So if SSO does not redirect users back to the client site as expected check out any other login related modules enabled on the controller site.
Comment #4
zyxware commentedYou should also take a look at this patch that will make the sso redirect respect the destination querystring as well - #807104: SSO does not respect the destination querystring
Comment #5
decibel.places commentedI too have multisite and when I log into client site I am redirected to contoller site
it happens after I add the controller URL in client single signon admin settings
I tried the patch in #807104: SSO does not respect the destination querystring but it does not help
I wonder if my db tables are set up right, the controller site has no prefix and the client site is installed in the same db with prefix "zinsuldata_"
so I added this to settings.php of the client multisite
status report says tables successfully shared
I also noticed that the database password "p=pBU(OMETP}" was converted to "p%3DpBU%28OMETP%7D" in the client site by the Drupal installer, but still seems to work
Comment #6
zyxware commented@decibel.places - Can you please see if there are any login redirection modules like login destination installed on the controller site? The patch provided at #807104: SSO does not respect the destination querystring only adds the support for destination querystring. That is not the issue that you are facing here.
Comment #7
aaron1234nz commentedThis is easily fixed with a one line change in the singlesignon_client.module.