Needs review
Project:
OAuth Connector
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
30 Dec 2010 at 00:16 UTC
Updated:
13 Apr 2015 at 17:11 UTC
Jump to comment: Most recent
Comments
Comment #1
voxpelli commentedThis is my highest priority right now - will hopefully have something to push during the day that reassembles how the Twitter module handles multiple external accounts connected to a single drupal account.
Comment #2
voxpelli commentedApparently needed to refactor all the databases of the OAuth module to accomplish this - will take a bit longer. I've multiple external accounts able to connect to single local accounts - but keys and secrets can't reliably be connected to them right now.
Comment #3
voxpelli commentedGot most of this working now. The fix for the OAuth module has been committed and is pending release. Now I just need to wrap this up, test it and then commit it to CVS. Should happen in a week or two.
Comment #4
dob_ commentedsubscribe
Comment #5
voxpelli commented"A week or two" - well - the code is committed and will appear in a dev-release. Not release ready yet though - some crucial parts are missing I think.
Comment #6
diginoon commentedhi voxpelli and merlinofchaos,
any update on this for use with 7? Or any kind of production use?
what would be required to make this work??
Comment #7
durum commentedsub
Comment #8
Leeteq commentedHave this been addressed for 7.x?
Comment #9
vinoth.3v commentedany update?
Comment #10
Firetracker commentedHi,
Has this been handled? The FBOauth module does it very nicely! Really need this feature in Connector...
Cheers
Zap
Comment #11
xbrianx commentedWhat's the status on this, its almost 3 years old now with it being the highest priority. Can we connect existing user accounts? If so how do we go about doing this.
Comment #12
angheloko commentedInterested... subscribing.
Comment #13
mjkovacevich commentedThis issue is almost a show-stopper for my clients. As far as I can ascertain if you register an account with one service, for example Google, you cannot then connect this Drupal account with another service, for example Facebook. The functionality of the modules seem to imply that a user can access and manage their connectors but I think the functionality comes up short.
Users today have multiple net personas, Google, Facebook, LinkedIn, etc. and it is essential to allow them to use any one of these "main-stream" services to login/register with a website/web app.
Android does this seamlessly and has done almost since inception. Why is the Drupal world so far behind?
Also, are the Oauth, Connector, Oauth Connector modules dead as they do not seem to be maintained/improved. I was really hoping to use "pure" community stuff to get the required functionality but might have to resort to free (read restricted/basic) commercial options like Gigya, Janrain, etc. :-(
Comment #14
voxpelli commentedI haven't been involved in Drupal development for a few years, but there are some other co-maintainers who are.
Regarding this issue, a quick glance at the code seems to suggest that this is indeed implemented in the Drupal 7 version as well: http://drupalcode.org/project/connector.git/blob/46cade3620061a41b385337...
Comment #15
swishstar commentedHere's a possible solution for you at https://www.drupal.org/node/2294449.
Comment #16
pianomansam commentedI've taken swishstar's work, expanded upon it, and created a separate module to solve this issue: https://www.drupal.org/project/oauth_connector_email
I'm also changing this issue's project back to OAuth Connector as that seems to be where this issue originated.
The OAuth Connector module currently already has a way to connect an existing user to a new OAuth Connection: /user/{uid}/connections. However, it doesn't provide a way for a user to be connected into their existing account upon login. As the above comments point out, this is the largest use case. The issue stems from the fact that there isn't something reliable and unique across accounts to know if a user should be associated. Probably the most reliable field is the email field, but email is not part of the core of OAuth implementation. In fact, Twitter didn't include it in the initial authorization until very recently. So I think this is why OAuth Connector has been released without the ability to associate existing accounts. And that's also why I've created a separate module to provide this feature. Take a look at the module and its code. Let's see if we can get this resolved.
Comment #17
Exploratus commentedThe module file is empty pianomansam. Is it just me?
Comment #18
pianomansam commented@Exploratus, sorry about that. That should be resolved now.
Comment #19
Exploratus commentedThanks. Will test. Really appreciate it!
Comment #20
omarlopesinoThe module of pianomansam (#16) worked for me.