Closed (fixed)
Project:
Gigya - Social Infrastructure
Version:
6.x-1.x-dev
Component:
Social network integration
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
27 Sep 2009 at 23:53 UTC
Updated:
13 Dec 2009 at 10:11 UTC
Comments
Comment #1
japerryFrom what you're telling me, I think I know what you hit on. Tell me if the following is what you did...
Created a user via drupal (not gigya), and logged in
Navigated to the user edit page --> Social Networks and connected to Twitter and Facebook
* When you connected to these, it should have prompted for username/password and allow access
Logged out of your drupal account
Clicked on the Twitter or Facebook icon, which had a brief popup, and then brought you to a new user login page
-------
If this is what you did, this is the expected, albeit unfortunate, functionality for the module. Since you connected your drupal account to facebook/twitter, you put in the authentication details which is stored locally in a cookie on your computer. Since you were still logged into twitter and facebook after logging out of your drupal account, gigya just sees the request to use the social network and lets it pass. (since you're logged in)
The problem however is that being 'connected' to a social network is different than being 'authenticated' by a social network. This issue has been passed on to the gigya team, and we're working on a way to tie social network accounts that were connected to a drupal account into the authentication system.
Hope that wasn't too confusing ;-) Please let me know if I can clarify anything here.
Comment #2
cpelham commentedAhh. I grasp the issue. Yes, I believe that is what occurred. I hope that eventually there will be a way to overcome this limitation as I believe it will be confusing for users.
Comment #3
domidc commentedNot sure if this is the right issue. But since I ve had the same problem I wondered why authenticate users with the social network and then let them register on the drupal site? The whole point of logging in with a social network user is to not having to register again.
Why cant the module create a (virtual) drupal user and connect that user with the social network user and then log the user in automaticaly? (email can be asked for later)
Right now it is confusing, the user is asked to log in with the drupal form and with social button. When he uses the social button and doesnt have a connected account on the drupal site he is asked to register. When a user registers the drupal way and then connects his user to his account later he is not connect in the gigya table. (Not sure if this is a bug or by design that existing drupal users cant login.)
There should be a unified way to connect social network users to drupal users.
1 An existing user should have a connection record in the gigya table
2 A new user should be registered and connect as a drupal user when he logs in with the social network account
Hope this made sense.
Comment #4
japerryThe main issue around auto-creation of a user are these two fringe cases:
a) social network provider gives too little information to the gigya module, making it hard to build a username
b) even if the username is given (say based on provider nickname), what happens when its in use? having usernames that say 'gigya-johnb' doesn't look too great either.
In alpha testing, we had the ability to join an existing user. However, we found this caused issues with syncing to the gigya network, and had to pull this functionality. gigya is aware of this issue and is working to find a solution to it.
Comment #5
azinck commentedsubscribing
Comment #6
azinck commented--deleted--
Comment #7
Rhino commentedsubscribing
Comment #8
Gigya commentedWe just release a module that includes support for "linking". this should solve the issue that cpelham has been talking about by allowing users that authenticate through Social Networks to map those identities to their existing Drupal users.
I'd be happy to get your feedback on this implementation.
Comment #9
Gigya commentedClosed unless any of you guys have any comments about this.