Gigya module conflicts with oAuth module [#929786]

Comment #1

azinck commented 5 October 2010 at 01:26

Thanks for reporting this. I have plans to implement Gigya's new PHP SDK http://wiki.gigya.com/032_SDKs/PHP which should allow us to avoid this problem.

Log in or register to post comments

Comment #2

decibel.places commented 5 October 2010 at 01:28

the recent trend has been for modules to use other helper modules (like oAuth) as components rather than duplicating functions

since I need oAuth for the Twitter module, it would be nice if you can also integrate it or at least not duplicate it

Log in or register to post comments

Comment #3

azinck commented 5 October 2010 at 01:40

@decibel.places

I hear you, but we need VERY little from oAuth (just one encoding algorithm) and that is now baked into Gigya's PHP SDK. I'd like to move to using Gigya's own SDK rather than maintaining one ourselves, and that pretty much means taking it as it is rather than rewriting it to remove their oAuth code. It seems like the obvious choice since the code is already there and will be maintained by Gigya rather than us (or me).

Log in or register to post comments

Comment #4

thedavidmeister commented 18 November 2010 at 05:14

I'm also using oAuth purely because the twitter module requires it (and the twitter integration of the Notifications module requires the twitter module).

I'm using twitter to keep contributors to my page up to date, so i can't disable that module but I want to build a new lower level user base for my site..

I'm looking at either waiting for an implementation of oAuth Connector http://drupal.org/project/oauthconnector that includes facebook's OAuth, or using Gigya to handle user logins..

it looks like there's a clear solution to this problem, whereas it seems hazy as to whether the oAuth Connector will ever prioritize facebook (they claim it's duplicating Facebook Connect's efforts).

is there a rough eta as to when this issue will be addressed/prioritized/looked at? knowing this would help my peace of mind a lot..

not trying to be pushy, just curious as to where we stand, and letting you know that more than one person is interested enough in your project to consider this important :)