Account Pending Registration if I try to sign up via social sites [#2341253]

Hi,
I am implementing gigya 7.x-4.5 on Drupal 7 website and facing the problem in social login.

Following issues are observed in case of Social Login
User creates an account with any Social Login ID. The module allows the user to create an account on the site with the Social Login ID. Hence, the user is a registered user on the site(account created via social login). In case the same user at later stage, tries to sign in into the site with the same social login ID, the site does not allows the user to sign in into the site, instead it throws an error that *Email already exists*, which is not the expected behaviour.
If user tries forgot password with same social account email id, the site returns “No username or email id found” error to the user.

// I have checked the configuration from https://console.gigya.com setting seems perfect.

gigya._.apiAdapters.web.callback({
  "errorDetails": "Missing required fields for registration: username",
  "errorMessage": "Account Pending Registration",
  "statusCode": 206,
  "errorCode": 206001,
  "statusReason": "Partial Content",
  "callId": "103c80beb80f47568c9f496a61c94683",
  "context": "R139456877",
  "Reason": 0
});

Expected output is "It should not ask for unsername in case of social logins"

Comment	File	Size	Author
	gigya-error.jpg	113.84 KB	RavindraSingh
#6	4.jpg	187.16 KB	RavindraSingh
#6	3.jpg	214.22 KB	RavindraSingh
#6	2.jpg	178.41 KB	RavindraSingh
#6	1.jpg	80.58 KB	RavindraSingh

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

RavindraSingh CreditAttribution: RavindraSingh commented 19 September 2014 at 08:34

Title:

Account Pending Registration if I try to logged in via social sites

» Account Pending Registration if I try to login via social sites

Comment #2

RavindraSingh CreditAttribution: RavindraSingh commented 19 September 2014 at 09:35

Title:

Account Pending Registration if I try to login via social sites

» Account Pending Registration if I try to sign up via social sites

Comment #3

Gigya CreditAttribution: Gigya commented 5 October 2014 at 15:20

Hi Ravinda,

We need some more information in order to reproduce this error.

Please provide the following to your Gigya Implementation manager:
- Your Gigya partner ID and API key
- access to your Drupal admin panel

Comment #4

Gigya CreditAttribution: Gigya commented 20 October 2014 at 10:42

Status:

Active

» Postponed (maintainer needs more info)

Comment #5

Gigya CreditAttribution: Gigya commented 20 October 2014 at 10:44

Status:

Postponed (maintainer needs more info)

» Closed (cannot reproduce)

Comment #6

RavindraSingh CreditAttribution: RavindraSingh commented 29 October 2014 at 06:32

File	Size
1.jpg	80.58 KB
2.jpg	178.41 KB
3.jpg	214.22 KB
4.jpg	187.16 KB

I am adding steps to reproduce with screenshots.

1. Config Gigya module with RaaS on Drupal site.
2. Enable RaaS login/register block for front end. (1.jpg)
3. Click on the Facebook icon from front-end as (2.jpg). Fill the credentials and hit the login button.
4. All APP the access your required info (3.jpg).
5. You will get redirected on the origin (4.jpg). Now it doesn't login you automatically it ask you to fill the form.
If you fill the form and submit. it doesn't take you logged in area (Acceptance Criteria: Social Login should not ask to fill the information and should login if authentication from app has been successfully completed).
When I checked the response it asks "username required". but in gigya setting username is optional.
There are two major concern in a case of social login.
1. It should login automatically.
2. It should not ask users to the data after returning from social sites.

Please let me know if anything is not clear.

Comment #7

RavindraSingh CreditAttribution: RavindraSingh commented 29 October 2014 at 06:32

Status:

Closed (cannot reproduce)

» Needs work

Comment #8

Gigya CreditAttribution: Gigya commented 29 October 2014 at 17:06

This is not a bug. And it's definitely not related to the Drupal module.
This is all about they way you designed and configured your RaaS screen-sets and schema.
And the behavior you are describing is not the default behavior of the RaaS OOTB, it is due to your screen-sets customization.

1. In your site "username" field is defined as a required fields (it is not defined as required by default OOTB, but someone changed it in your site to be required). You can change that using the UI Builder, or by using the accounts.setSchema API method.
See in the UI builder guide how to switch on/off required fields:
http://developers.gigya.com/010_Developer_Guide/10_UM360/040_Raas/020_Sc...
An alternative solution - if you prefer keeping "username" as a required field, make sure to add it to the "complete registration" screen (the screen from 4.jpg), this way the user will be required to enter his username and the registration will complete successfully.

2. When you have one or more fields defined as required in your site schema (usually email is a required field, and in your case username is a required field as well), after returning from social authentication, in case the social site did not provide one or more of the required fields, then you will be redirected to the "complete registration" screen (the screen from 4.jpg) to fill in the missing required fields (e.g. email & username) which were not provided from your social data.
Please refer to the RaaS guide: http://developers.gigya.com/010_Developer_Guide/10_UM360/040_Raas
And specifically take a look at the Registration flow:
http://developers.gigya.com/010_Developer_Guide/10_UM360/040_Raas#Regist...