Might want to look into what voxpelli has been doing with the Connector module. It seems like he's interested in pretty much the same thing, but he's focussing on trying to make it pluggable. There's also Janrain and Gigya, but I imagine the whole point of your effort is to side-step the third-party API, huh? :)

Any chance you'd be open to merging efforts or getting in touch with him?

Comments

voxpelli’s picture

voxpelli commented

Subscribe - I'm very actively developing my module and will soon push a new release

mauritsl’s picture

mauritsl commented

Didn't know the Connector module yet, thanks for your notice.

Both tends to do the same, but they are very different.

It is somewhat hard to setup the oauth connector module. It's not clear what you have to fill in as resource and field. Its better the have the settings for several services in the readme instead of a link on the project page.

I got an exception after returning from Twitter, so I haven't test everything yet. The exception was "Exception: Failed to fetch data from url "http://api.twitter.com/oauth/access_token" (HTTP response code 401 Unauthorized):".

Differences as far as I can see:

  1. ServiceConnect has a submodule per service. Connector can handle all OAuth services, but requires more knowledge (or: needs more documentation).
  2. Connector tends to keep the 3th party screenname via realname (right?). With Serviceconnect, users have to choose a username when they login for the first time.
  3. With ServiceConnect, you may force users to accept terms & conditions after they login. This can be a legal requirement for 3th party providers when you store profile data in your own database.
  4. ServiceConnect can map all 3th party profile fields to fields from both profile module and CCK fields for use with content profile.

I think it is a good idea to merge both efforts in the future. We can expand the field mapping part of the connector module with the (content)profile integration from serviceconnect. We can also make the realname part optional, and add a "register your Twitter profile" page like serviceconnect has. Then make this configurable to keep both options.

voxpelli’s picture

voxpelli commented

1. I have chosen to not have this in Connector since I believe this should be taken care of by Twitter.module and similar.
2+3. My primary goal has been one click login therefor I haven't done any work on this
4. Seems like a great thing - should probably have this in Connector!

I will push my latest, although not yet complete, code for multiple connections per user to Drupal.org now. Lets try and see how we can merge after that.

(I would like to excuse right away if I may be a bit slow to respond on any merging thoughts - I need to port the OAuth module to D7 asap if I'm not going to get beaten by an angry mob :P I will likely port Connector as part of that so I can make sure the OAuth module works on D7.)

MacRonin’s picture

MacRonin commented
Title: What makes this distinct from Connector module? » What makes "Service Connect" distinct from Connector module?

Updating title so it is more informative in dashboard activity list.
plus this lets me get updates without saying "+1 subscribe" :-)

I'm particularly curious about the Drupal7 status

frans’s picture

frans commented

Hi,

Can you take a look at connector and oauthconnector for D7? Some of the ideas of fields are already implemented, but could use more love.
I also build presets connectors for FB, twitter and linkedin. That should make it more easy to implement.

I really like to know your opinion!