Could you explain the difference between this module and Gigya Socialize please to help users understand which to choose?

Thanks,

Michelle

Comments

voxpelli’s picture

voxpelli commented
Status: Active » Fixed

I added a description to the project page: http://drupal.org/project/connector

The main difference is that Gigya is an API which Gigya Socialize only provides an integration of. That makes Gigya no different from all of the other modules that only integrates to a single third party authentication API.

Connector is all about providing a platform for all of those modules so that they can share the basic functionality and UI needed for such a service - and to also provide a single integration point for other modules who want to interact with such modules.

Please reopen if you feel that the description is lacking.

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented

Actually, Gigya lets you login with a 6 different services, not just one. So you're saying that this is an API that has the potential to connect with not just those 6 but any other service someone wants to write a module for? Sounds like a good idea in theory, provided the connection modules follow.

Michelle

voxpelli’s picture

voxpelli commented

Gigya is an external API that exposes 6 different services - the Drupal module only talks with that single API.

Connector currently supports Facebook Connect and the OAuth work that will soon be done will provide support for at least Twitter and MySpac. The rest of Gigyas services are OpenID-based and would require an OpenID connector which I've no plan on making since OpenID is included in Drupal core. But it should be possible if anyone would like to create such a connector.

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented

Ah, I see what you're saying. So this is more like Gigya itself rather than the Gigya Drupal module.

I think I'll give it a whirl. I was just about to start using Gigya. I have an account set up but hadn't gone through and added the services. I like the idea of having a Drupal native module rather than a service.

Michelle

Anonymous’s picture

Anonymous (not verified) commented

I would caution those who want to use Gigya that their terms of service for end users may not be what you want to expose members of your community to. I mentioned them in a post about authentication at http://learnbythedrop.com/drop/158.

Rob Safuto
Awakened Voice

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented

@awakenedvoice: Hmm... Yeah... I see what you mean. I guess this area just really isn't ready for use, yet. I was going to try Connector but I see the code isn't on drupal.org which is a major turn off for me. I think I'm going to hold off on adding this feature and see how things shake out.

Michelle

voxpelli’s picture

voxpelli commented

@Michelle: The code is on Drupal.org - we just haven't made any release yet. It's just the FBConnector that isn't here yet. And yeah - this module is like Gigya itself :)

adub’s picture

adub commented

Are drupal services using login/key supported or any plans for this? (sorry I'll open up a new issue)

voxpelli’s picture

voxpelli commented

@adub: Support for Services one way or another is on the list - OAuth will be the first kind of support.

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented

@voxpelli Well, my goal is to try and lure some FB users over so that's the important bit for me. I don't want to have my site dependent on something that you say probably won't ever be on drupal.org.

All I want is for me to post a link on FB about a forum post and have them be able to come over and comment super simple without having to go through the whole signup process. I didn't realize it was going to be this hard to do... :(

Michelle

pribeh’s picture

pribeh commented

I know the issue queue isn't typically the place to do this: but I want to chime in with my support for this project. I absolutely support a Drupal native framework for connecting Social networking sites. I understand that it might take an unusual amount of cooperation, time and commitment from other module developers (I'm thinking of Twitter and Facebook Connect modules) but I it would be great to see it happen so that a unified approach to handling integration with social networks emerges. From a designer's perspective having a unified UI to work with makes total sense. I'm going to try this module right now.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

iainhallam’s picture

iainhallam commented

Re. your comment on OpenID, the current implementation in Drupal isn't the easiest to use; in the interests of merging UIs, would an OpenID connector be relatively easy to create?

voxpelli’s picture

voxpelli commented

@ianhallam: Well - one thing that would be different with an OpenID connector compared to an OAuth one is that an OpenID connector needs additional input-elements besides the single button that is needed for OAuth.

An OpenID connector would probably be built upon the existing OpenID modules and how easy or hard it is to adopt them for a different UI I don't know.