Gigya Job Openings

Google

Skip to end of metadata
Go to start of metadata

 

This page is a step-by-step guide for the process of opening and setting up an external Google application as part of the Gigya Setup process.

Note: If your site is defined under one of Gigya's non-US data centers, replace domain references to "socialize.gigya.com" (or "socialize.us1.gigya.com") with https://socialize.<data_center>/

Where <Data_Center> is:
  • us1.gigya.com - For the US data center.
  • eu1.gigya.com - For the European data center.
  • au1.gigya.com - For the Australian data center.
  • ru1.gigya.com - For the Russian data center.
  • cn1.gigya-api.cn - For the Chinese data center.

If you are not sure of your site's data center, see Finding Your Data Center.

Domain references are defined in Gigya's dashboard, externally in social network app definition pages, and when using Gigya's SDKs to set the domain (in particular the APIDomain field in class GSRequest). 

Google Plus Deprecation FAQ

Google has announced they are accelerating the deprecation of all their G+ APIs. This begins on January 28, 2019 and will complete on March 7, 2019. 

  • Does the deprecation of Google Plus affect me?
    • Yes, if you are using Google as a login provider then you will need to take some action for Google to continue to function properly, as detailed below. We expect the transition to go smoothly, thanks to the following:
      • The OIDC login flow has been supported for some time, meaning users should continue to be able to log in using their Google identities.
      • Our tests show that the providerUID returned from Google is the same for Google Plus and Google Sign-In, so user records will update seamlessly after the change.


  • What do I need to do to ensure the Google login option will work smoothly?
    • After your Provider Configuration is updated, if you are using the General Permission of Enable retrieving user contacts you will need to stop requesting that permission by unchecking the box and re-saving your site's Permissions.


  • Does the deprecation affect my mobile apps?
    • Yes, any mobile apps that are using Google as a login provider via our Android SDK need to be updated and recompiled with the latest SDK to support the Google Plus deprecation. Download the latest Android SDK (v3.3.28 or above):
      Gigya Developer Downloads

 

 

Phase 1 - Setting up a Google Application

Creating a project

  1. Go to the Google Developers Console at https://console.developers.google.com.
  2. Click the Select a project menu to open the Projects screen, then press the NEW PROJECT button add a new project.




  3. In the "New Project" box:
    • Enter a Project Name.
    • Define whether or not to attach the new project to an organization. 
    • Click Create
    • You will then arrive at the projects Dashboard.


Selecting your APIs for use with Gigya 

  1. Click ENABLE APIS AND SERVICES (above), scroll-down and select "Google People API" (under 'Social APIs').
  2. On the following page press the ENABLE button.
  3. Press the Create Credentials button on the next page to create your credentials, on the right.


Get your Google credentials

  1. Google supplies a brief questionnaire to help you configure your app. Simply answer the questions and it will direct you to the proper credential type for your app. Since we are using the People API for the web, we will choose those and select User data as what we will be accessing. When finished, click What credentials do I need?.


  2. The system should now direct you to Create an OAuth 2.0 client ID. Give your app a name and enter your Authorized redirect URIs in the respective fields. If you are not using a Cname, these will be:

    https://<DataCenter>/GS/GSLogin.aspx?

    Finding Your Data Center

    The URIs must include the trailing "?".


    When complete, press Create OAuth client ID.





  3. Next, you will need to configure your Consent screen. You must input a valid email address and name your app as you would like it displayed to users. Then click Continue.



  4. You will now be presented with your Client ID. You can download it as a JSON file or copy it, and then click Done.



  5. You will be taken back to the Credentials tab of your project. To view the it's configuration, click on the app name on the left. 


  6. Before you can add your Authorized JavaScript origins, you must add your site(s) to the Authorized domains by going to the OAuth consent screen section. Enter any domains that will be hosting the app.



  7. While still on the OAuth Consent screen page, enter all your links, i.e.:
    - Application Homepage link
    - Application Privacy Policy link
    - Application Terms of Service link

    On this tab you can also view the current permissions for your app in the Scopes for Google APIs section:


    When done, press Save.

  8. The last thing still to do is to get your secret key. While on the Credentials page of your project, click the pencil icon to Edit the app.
     

    Here you will be able to view or reset your secret key:


  9. That's it. Your app is now ready and you can proceed to Phase 2, below.

 

Phase 2 - Configuring Google Application Keys in Gigya's Website

Setting your keys in the Google Configuration Editor

  1. Log into your Gigya account and go to the Providers Configurations page of Gigya's Console.
  2. Click on Google to open its configuration window.

  3. In the Google Configuration window enter:
    • Your "Client ID" from the Google Developers Dashboard into the "Consumer Key" field. (The entire string, including .apps.googleusercontent.com)
    • Your "Client Secret" into the "Secret Key" field.
    • If you are using a CNAME, be sure to select the "Enable CName" checkbox.
    • Select Secure redirects only to allow only HTTPS redirects from Google.
    • Selecting "Enable Native SDK Capabilities" is required to enable automatic login. For more information see Native SDK Capabilities.
  4. Click "OK".
  5. Click "Save Settings" on the bottom right-hand corner.

 

That's it, Google configuration is complete! Please note that it might take up to 10 minutes for our system to become synchronized with Google.

 

Additional Information

App Verification

To ensure the best possible user experience when users engage your app, you will now need to get it verified by Google. The verification process can take between 3 and 7 business days and possibly longer, so should be started as soon as possible after creating and setting up your application. If you do not get your app verified, whenever users log in to your site using your Google App they will be presented with a warning screen stating This app isn't verified (it is important to note that the number of users able to use an unverified app via passing through the warning screen will be capped at an undisclosed number of users determined by Google. See https://developers.google.com/apps-script/guides/client-verification for more information). 

The steps necessary to get your app verified are as follows:

For additional information, visit https://support.google.com/cloud/answer/7454865.

 

Unable to render {include} The included page could not be found.