I have found following error while setup SSO in client site: cant login anymore to Client site.

I put following codes to settings.php of "Client" site as per instructed
in Readme.txt:

$conf['session_inc'] = 'sites/all/modules/sso/session.singlesignon.inc';
$db_prefix = array(
'default' => '',
'authmap' => '',
'sessions' => '',
'users' => '',
);

I do not have database prefix (both in drupal1 and drupal2 site)
and I have two databse in same machine one is "drupal1" and another is "drupal2"
(separate setup)

Here noted that Controller site installed successfully and I got private key etc.
and in contrller sites settings.php I put
$conf['session_inc'] = 'sites/all/modules/sso/session.singlesignon.inc';

Here also noted that I am not understanding what's writtent in
end part of Readme.txt:
Where I need to put below code???
----------------------------------------------------------------------------------------------------------------------------
On MySQL, you can use 'database_name.' as a prefix to share the tables
directly from the controller's database, and use a blank prefix for the
client tables (which reside in the client database):

$db_prefix = array(
'default' => '',
'authmap' => 'controller_database.',
'sessions' => 'controller_database.',
'users' => 'controller_database.',
);

------------------------------------------------------------------------------------------------------------------------------------

Error message:

Warning: Unknown column 's.domain' in 'where clause' query: SELECT u.*, s.* FROM users u INNER JOIN sessions s ON u.uid = s.uid WHERE s.sid = '32c56e465cd48d61c85863972fb2c4ee' AND s.domain = 'MY IP ADDRESS(I JUST DELETE)' in C:\xampp\htdocs\drupal2\includes\database.mysqli.inc on line 128

Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at C:\xampp\htdocs\drupal2\includes\database.mysqli.inc:128) in C:\xampp\htdocs\drupal2\includes\bootstrap.inc on line 1037

Warning: Cannot modify header information - headers already sent by (output started at C:\xampp\htdocs\drupal2\includes\database.mysqli.inc:128) in C:\xampp\htdocs\drupal2\sites\all\modules\sso\client\singlesignon_client.module on line 38

Warning: Cannot modify header information - headers already sent by (output started at C:\xampp\htdocs\drupal2\includes\database.mysqli.inc:128) in C:\xampp\htdocs\drupal2\includes\bootstrap.inc on line 636

Warning: Cannot modify header information - headers already sent by (output started at C:\xampp\htdocs\drupal2\includes\database.mysqli.inc:128) in C:\xampp\htdocs\drupal2\includes\bootstrap.inc on line 637

Warning: Cannot modify header information - headers already sent by (output started at C:\xampp\htdocs\drupal2\includes\database.mysqli.inc:128) in C:\xampp\htdocs\drupal2\includes\bootstrap.inc on line 638

Warning: Cannot modify header information - headers already sent by (output started at C:\xampp\htdocs\drupal2\includes\database.mysqli.inc:128) in C:\xampp\htdocs\drupal2\includes\bootstrap.inc on line 639

Comments

Yuki’s picture

Yuki commented
Title: NEED HELP PLEASE » NEED HELP PLEASE Warning:MESSAGE
jarchowk’s picture

jarchowk commented

Actually I'm getting the same message as well. I tried setting up a multisite setup using:

$db_prefix = array(
'default' => '',
'authmap' => 'controller_database.',
'sessions' => 'controller_database.',
'users' => 'controller_database.',
);

Double checked all of my installation steps in the readme file. Any ideas?

meba’s picture

meba commented

Yuki: changing the subject won't speed up solving this support request.

You need to read the howto again. it is essential that both clients and controller share sessions, authmap and users tables.

jarchowk’s picture

jarchowk commented

Gotcha. default install had a $db_prefix = ''; later in the code.

FYI I ran into a this problem:
http://drupal.org/node/596034

Fixed it fine, works great! Thx for the module.

Yuki’s picture

Yuki commented

Jarchowk don't know still what to do.pls help me as I am novice.How did u solve this issue?

Yuki’s picture

Yuki commented

Still trying to find out the solution but everytime getting errors. Did several trials after reading readme.txt. I hope somebody would help me to overcome the problems.

bleen’s picture

bleen commented

I had this issue and the only solution was to disable the controller module AND uninstall it (using the uninstall tab on the admin/build/modules page) .... then enable the controller module again

Basically, start the whole process over but make sure you uninstall the module

twinfinity’s picture

twinfinity commented

@all replies :

It may be interesting to know that the cause of the above warnings is the use of different users for databases. For the single sign on module to work, all databases must have the same user ( preferably the root user [ same details as cPanel login ]. Unlike other scripts, Drupal does not require a "root_user" entry for database username to establish a database.)

espirates’s picture

espirates commented

why is there a dot after controller_database.', ?

isn't it suppose to be 'our_database' ? or are we suppose to use controller_database.our_database

meba’s picture

meba commented

No, it's supposed to be our_database.

espirates’s picture

espirates commented

Yeah I figured that out in the end, although it doesn't say anything about the dot in the read file. It would be nice if instructions were clearer. Something like "leave the dot in there" or something. Great module.

picxelplay’s picture

picxelplay commented

@twinfinity

It is not wise to have your cPanel login the same as your drupal logins/drupal dbs. If someone gets this info, you now have security holes in your whole cpanel account, not just drupal. It is wise to make separate logins for everything, therefore minimizing the exposure to a hack. If you do get hacked, and you have separate logins for everything, then only that section is compromised; and not your whole operation.