Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
We were poking around the code and is seems that the modules uses wrong ID for loading GigyaUser object.
Bit of context:
.../gigya/gigya.module:134
// If the user is logged in then attach the Gigya object to the
// user object.
if (user_is_logged_in()) {
global $user;
// Attach the Gigya object to the user object.
GigyaUser::load($user);
calls
public static function load(&$account) {
// Attache to user if the user is logged in.
$account->gigya = (isset($account->uid) ? new GigyaUser($account->uid) : NULL);
}
Where $account->uid
is just Drupal ID. But it should be Gigya ID which looks something like "17e4399180968c8bdadd64b7a74a4cfc" and this is available in $_SESSION['gigya_raas_uid']
More details to be considered:
* we are using RaaS only - maybe this is not true for non-RaaS configs
* It's probably on more places - gigya.module:134 is just first I found while creating the issue.
Comments
Comment #2
radimklaskaComment #3
dabbor CreditAttribution: dabbor commentedI do agree with Radim, I saw and debugged that code too.