Problem

After implementing the gigya raas solution, our watchdog log was overflowed with the following 3 messages (in sequance):

  • Access mode app
  • errorcode :
  • Response from gigya callId : ********************************apicall:getUserInfo,Error:

These errors are caused when the gigya module tries to load a gigya user with the drupal user id, this happens whenever the login mode is not Drupal, and you try to display a user entity.

Proposed resolution

The gigya_user_view function has the account uid as the gigya user id hardcoded and ignores raas mappings.
My solution is to try to load the gigya UID from the raas extra mapping variable and only if it fails, use the account uid.

CommentFileSizeAuthor
#5 load-gigya-user-by-raas-extra-mapping-2926298-5.patch3.57 KBeyal shalev
#2 load-gigya-user-by-raas-extra-mapping-2926298-2.patch3.59 KBeyal shalev

Comments

Eyal Shalev created an issue. See original summary.

eyal shalev’s picture

eyal shalev
he/him
commented
Status: Active » Needs review
StatusFileSize
new load-gigya-user-by-raas-extra-mapping-2926298-2.patch3.59 KB
eyal shalev’s picture

eyal shalev
he/him
commented
Issue summary: View changes
gg24’s picture

gg24 commented
Status: Needs review » Needs work 
  1. +++ b/gigya.module
@@ -900,35 +900,50 @@ function gigya_user_view($account, $view_mode) {
+      $bio         = $_gigya_user->getUserInfo();

    Seems the indentation is not as per standards. 

  2. +++ b/gigya.module
@@ -900,35 +900,50 @@ function gigya_user_view($account, $view_mode) {
+          $account->content['gigya'][$network['provider']]        = array(

    Indentation is not as per standard.

eyal shalev’s picture

eyal shalev
he/him
commented
Status: Needs work » Needs review
StatusFileSize
new load-gigya-user-by-raas-extra-mapping-2926298-5.patch3.57 KB

Fixed the indentation

FYI - the indentation issue exists in the original code - I just didn't want to update it as well.