Gigya encountered an error while validating itself

I am getting this error, as well.

I am getting this error also.

I am getting this error also
6.x-2.2 version of gigya.com, drupal 6.19, php 5.3.3, Apache/2.2.16 (Ubuntu), MySQL database 5.1.49

I also got this error on the gigya localize settings page, when I was running version 2.2

I checked the logs and there are a lot of notices, but no errors, in spite of some of the log messages appearing error-like. I have a few "403005 Forbidden. Unauthorized user" notices and a few "_gigya_request_failure (0):results ..." and a few "gigya_getUserInfo failure".

When trying to log in via social networks, the following error is encountered: "Failed connecting. Please try again later"

I upgraded to the 3.x dev branch to see if that would solve the problem, but I'm still getting this error :(

Make sure your server's time is set properly. Alternatively, this could be due to a change in the Gigya API. The module has been using a quirky technique on the admin page to check if the API key works and the API may be responding differently to the request. I'll look into it (haven't set up a Gigya dev environment on my machine yet so that's why I can't look at it right this second).

subscribe. I'm also getting this error. What do I do to ensure server time is set correctly?

I just reconfigured my server's timezone settings in WHM to match what is on my drupal site (timezone Australia/Melbourne in both), and clicked "Sync time with time server", so it should be exact.

I'm still getting the same error:

s:41:"Gigya API error 403005: Unauthorized user";

location: http://www.beat.com.au/admin/settings/gigya

referer: http://www.beat.com.au/admin/settings/date-time/configure

Ok, thanks for the updates. It sounds like the Gigya service just doesn't like the wonky way we were checking the API key. Thankfully the fix should be easy. Stay tuned.

Subscribing, as I'm also getting this error. Any rough ETA for the fix?

sobscribing

subscribing

I wasn't able to reproduce the issue but I took a stab at it anyhow -- see if this patch fixes it for you.

No, this does not solve the problem. If you read the documentation on that function, you can see why we were using admin for UID.

/**
 * Validates the Gigya session keys.
 *
 * We use the site 'admin' username to find out the status. If it shows the
 * user logged out, thats good, if it returns an error then our keys are
 * most likely bad.
 */

Here's how to reproduce the error.

1) install Drupal
2) add the gigya module (the 3.x dev branch) into sites/all/modules
3) visit your site's module page (at /admin/build/modules)
4) enable the gigya socialize module
5) visit the gigya settings page (at /admin/settings/gigya)

BAM. error.

Okay, I spent a bunch of time trying to figure out why nothing was being logged correctly in watchdog and I found a few places where the $string and $args being passed in weren't matching up quite right. This patch does not fix the problem with validation, but it does get watchdog properly logging errors from Gigya now. Baby steps.

The error Gigya is throwing for me here is "Gigya API error 403005: Unauthorized user"

attaching the patch might help :/

Jen,

I understand why admin was being used as the UID. And I saw that error 403005 was being thrown (though I have still been unable to reproduce this). I assumed that Gigya may have changed their API to reject 'admin' as a UID and throw a 403005 error. Thanks for the feedback that the patch didn't work for you.

Since I'm unable to reproduce this it's very hard for me to guess at what's going on. I suppose I'll create a new Gigya site account on the off chance that there's something different about new accounts compared to my older one.

subscribing. Same error here.

@azinck

You don't even need to have gigya keys to get this error - you get it even before you enter any keys at all into the settings page. The first time you visit the page it throws the error.

Hm... I had originally assumed that a gigya_validate function would be needed often, but after I was told that it might not even be necessary I checked the code, and sure enough the only place that function is ever called is when the admin form is being built - which is weird enough as it is!

I say we just get rid of it and close this issue :) Here's a patch that deletes the validate function entirely.

subscribing...

@ambiance7
could you test my patch?

and changing the title back to something more descriptive :)

Subscribing as I'm having this problem as well on a fresh install

@Deathnerd can you test my patch? Instructions on applying patches can be found here: http://drupal.org/patch/apply

@jenlampton - your patch works for me. Thanks.

@jenlampton I ran your patch, and got this result:

patching file gigya.admin.inc
Hunk #1 succeeded at 84 (offset 63 lines).
patching file gigya.inc
Hunk #1 FAILED at 114.
Hunk #2 FAILED at 354.
Hunk #4 FAILED at 595.
Hunk #6 FAILED at 636.
4 out of 6 hunks FAILED -- saving rejects to file gigya.inc.rej

I am using version = "6.x-2.2"

Also, I don't know if anybody has encountered this, anonymous users don't see my social network icon (i only enabled Facebook), but they DO see the block title "Log in using a social network". When I am logged in I can see the icon fine...

@thexman - I ran the patch against the latest code in CVS

@mrfelton - thanks, the patch worked without a problem now.

Still not seeing my social icons, though. Only the title of the gigya block....

thexman:
Turn in the Gigya settings page un-check the "Friends" box in required capabilities.

I just tested this and it's indeed a bug.

@jenlamptop, I can't quite review your patch because it's in a weird format. The -up switch makes it more readable (and it plays nice with Dreditor :)) for easier reviewing.

Also the attached patch looks like it just removes the gigya_validate function, I don't think this is the right approach. It is weird that the validate function is running on form build, maybe we can move it to an actual validate function for the form that way this will only run when a user changes the value of the form.

I'm having the same problem. I installed the Gigya module and I keep on getting the error, "Gigya encountered an error while validating itself. Please check watchdog and try later. If this message keeps appearing please contact gigya or file a bug in the gigya project issue queue." Additionally, my social icons don't appear in their blocks, but only the titles of the icons appear.

This module looks like it has great potential so does anyone have a solution for this?

Hi thexman.
I applied the patch cleanly I think that it was made against the 6.x-3 branch.
I'm using 6.x-3.0-beta3.

I'm not sure why you think the patch is in a weird format, that's what you get when you do a cvs diff, and it applies cleanly to the 3.x dev branch so you should have no problem testing it. Anyway, here's a version created with -up.

If we want to add something to validate I think that would be fine, but since this gigya_validate function does not actually validate the public and secret keys - all it does right now is throw an error 100% of the time, I say let's get rid of it until their API supports some way to actually validate the keys.

I think we shouldn't delete it all together we can just ignore/disregard these errors
I added a patch that does that.

you you use cvs diff -up to generate patches in the preferred format for Drupal.

sorry for that

with out the untracked file a the top
I need to get use to CVS

$ patch < patch.patch
patching file gigya.inc
Hunk #3 FAILED at 381.
Hunk #4 succeeded at 460 (offset 23 lines).
Hunk #5 succeeded at 475 (offset 23 lines).
Hunk #6 FAILED at 491.
Hunk #7 succeeded at 519 (offset 23 lines).
Hunk #8 succeeded at 534 (offset 23 lines).
Hunk #9 succeeded at 549 (offset 23 lines).
Hunk #10 succeeded at 566 (offset 23 lines).
Hunk #11 FAILED at 574.
Hunk #12 succeeded at 582 (offset 23 lines).
Hunk #13 succeeded at 601 (offset 23 lines).
Hunk #14 FAILED at 637.
Hunk #15 succeeded at 692 (offset 29 lines).
Hunk #16 succeeded at 702 (offset 29 lines).
4 out of 16 hunks FAILED -- saving rejects to file gigya.inc.rej

with the latest dev.

Looks like this has been committed to latest dev, but not set as committed.

Latest dev 3.x. doesn't work. I just installed everything, connected one account with gigya. And now that account is linked with all my drupal users. Every user in my drupal site isnow connected with that twitter account.

Gigya's 6.x module is deprecated. We no longer maintain this version. We encourage upgrading to our latest module.