Gigya Social Login and RaaS, how to activate it on your VirtualNewspaper

"More than 700 leading brands rely on Gigya to securely collect, manage
and leverage customer identities at scale, providing the unified customer view needed to create personal experiences, fuel top-line growth and promote enduring customer relationships. The journey starts here."  - Gigya Inc.

As soon as you contacted Virtualcom to communicate your intention to use Gigya on your VirtualNewspaper instead of the usual registration flow, you can proceed to configure it in the following way.

1. Configure your settings

Go to Settings in your back-office panel and scroll down until you see the Gigya Configuration panel. Here you are asked to fill the form with your data. (See image [1])

Fields explanation:

• Gigya API Key: (mandatory) The Api Key provided by Gigya relative to your Gigya Account
• Gigya Application User Key: (mandatory) The Application User Key of the application created on the Gigya Account. (see image [7])
• Gigya Application Secret Key: (mandatory) The Application Secret Key of the application created on the Gigya Account. (see image [7])
• Gigya Read-only fields: (optional) This field is relative to the "edit data" part of the VNP/Gigya user flow: where after an user has logged in the system, he could want to edit its own data, and going to "My profile", he will find a form with the summary of its own data, and the possibility to edit them. Since those fields are retrieved from Gigya Site Schema, they are cumulative of all the data collected from all the registrations to the system, even from social network, so it can happens that some unwanted fields appears on the fields list. So you will have two options: to make it read-only using this field, or to hide it, using the next explained field. Please inserts the fields as a comma separated list, and refer to the field name as it appear in the screenset mapping list (see image [2]).
• Gigya Hidden fields: (optional) please refer to the previous field explanation.
• Gigya RegistrationLogin ScreenSet ID: (mandatory, default "Default-RegistrationLogin") The Gigya ScreenSet String Identifier relative to the Gigya ScreenSet you would like to use as registration form. (see image [3])
• Gigya Data Center: (mandatory) the data center your Gigya Account is binded to, specified by your Gigya Console Admin (see image [4])
• Gigya Validation Extension Code: (optional) Here you can insert your custom validation JS code for the ScreenSet's fields validation. Please insert your code including <script> and</script> tags too, even more than one. When this field is not blank the Official Gigya Extension JS lib it's automatically included in the page (http://cdn.gigya-ext.com/screenset-validation.min.js). For more information about validation rules please refer to https://github.com/gigya/screenset-validation.

2. Configure your titles to enable Gigya on them

At this point you will just need to decide on which of yours newspaper title you would like to enable Gigya. 

To enable Gigya on a newspaper title, go to Settings and choose the title you would like to edit. Click on the gear icon (see image [5]) and scroll down until you will see the Gigya Enabled select (see image [6]), and change the state from OFF to ON, now click save.

Repeat this procedure on every title on you would like the enable Gigya.

3. "Gigya Console Admin" Suggestions & FAQ

• Where the email registration callback URL have to point to?
  We suggest to point it to www.yoursite.com/yourname/?userWelcomeMessage=true

4. Gigya Support

The contacts for support are:

• Technical: Shirly Leibovich <shirly.leibovich@gigya-inc.com>
• Account: Chris LaPierre <chris.lapierre@gigya-inc.com>