Skip to end of metadata
Go to start of metadata

Contents

Overview

Google Sign-In is a secure (OAuth 2.0) login method. BPD sites can implement a third party sign-on method with Facebook so users can be securely authenticated using just their Google credentials — the same account they already use for Gmail, Docs, Google+, and other Google services. For sites with B2B customers, you can also set third party logins to link to existing users. 




This article will guide you through the implementation of Google Sign-In for your site. 


Prerequisites

You'll need to be running version 3.96+ (and 4.16 for linking to existing accounts). The 'Third Party Login' feature must be enabled in the CMS. 


Step by step guide

1. Create a Client ID

To enable Google Sign-In, you'll need a Google API Console project & Client ID.

Follow the steps below, or use Google's guide to get started - https://developers.google.com/identity/sign-in/web/devconsole-project 

  1. Go to https://console.developers.google.com/project/_/apiui/apis/library and login to your Google account

  2. Select your API project from the dropdown, or create a new one

     or 

  3. Select the Credentials menu, and the OAuth consent screen tab.

  4. Select the email address, enter your Product (website) Name, and click Save.
    (You can populate the optional fields now too, if you choose.) 


  5. From the Create credentials dropdown, select OAuth client ID


  6. Select Web application and enter your site Name. Then enter your URL in the JavaScript origins field.

    Google advises as follows regarding JavaScript origins:



  7. Click Create, and you now have a Client ID!  Copy this down somewhere. 


2. Configure Google Sign-In 

 Now it's time to set up your website. 

  1. In the CMS, navigate to Settings → Feature Management → User

  2. Toggle on Third Party Login

  3. Click Configure.


  4. Toggle the Registration Page and Allow Linking options on/off as required. (Note - these settings apply to all single sign-on methods on your site. So if your site is also using Facebook Sign-in, these options may already be correctly configured.)


    The Configuration Settings are explained in the table below.


    OptionDescriptionExample
    Use Registration Page

    Displays additional registration fields to the user after they've signed in with Facebook/Google. You can use this to request more info from your customer before they click Login.


    (This screen is only shown on the user's first login.)

     


    If 'Force Linking to Existing Users' option is used, the 'Hide Registration Section' toggle in the Single Sign-on Login Registration Fields widget is enabled, and these registration fields will not be displayed.   

    Allow Linking To Existing Users

    Allows a user to login with a Google login, then link that login to an existing account on your site (if they have one).


    This retains all of the user's order history, favourites, etc, with the benefit of a quick Google sign-in.


    (This screen is only shown on the user's first login.)


    Force Linking To Existing Users

    For B2B sites

    This option must be ON for B2B sites because a user logging in with a single sign-on should be linked to an eligible User in an existing Customer account. 

    To complete implementing this method, the 'Hide Registration Section' toggle in the Single Sign-on Login Registration Fields widget must be enabled so that a Facebook user cannot register as an unlinked user.   

    Forces a user logging in with Facebook to link that login to an existing user on your site. If the user cannot link to an existing user, the system will not allow the login to be completed.   

    (This screen is only shown on the user's first login.)


    Default Role

    If this is left blank and the Facebook account holder is not linked to an existing User, a new User will be created with the Initial Role of 'PUBLICR'.

    Enter an alternate default Role if required.


    Default Customer Code

    If this is left blank and the Facebook account holder is not linked to an existing Customer account, the new User will be created with the Initial Customer Code 'WEBSALES' 

    Enter an alternate default Customer Code if required.


  5. Enter your Client ID from Google into the Sign-In Client ID field. 

  6. In the Token Info Endpoint field, enter the following: https://www.googleapis.com/oauth2/v3/tokeninfo?id_token={0}


  7. Enable Google Sign-In with the toggle, then click Save


3. Optional Customisations

Don't like the button text on the Registration page? Wish the login pop-up didn't use the phrase "social network"?  

No worries - you can customise this via the widgets!

(i) Change the text on the Registration / Link User page here: 

  1. Navigate to ContentPages & Templates.

  2. Search for and select the Third Party Login Registration template. 
  3. Edit the Single Sign-on Registration Fields widget
  4. Update the headings, button labels, and prompts here. 


(ii) Change the headings on the Login pop-up here: 

  1. Navigate to Content → Theme Layout.
  2. Edit the Login Logout Popup widget.
  3. Select the Titles tab to update the headings. 

Google Sign-In is a great way to get your customers logged in and shopping with you faster. And your users will no doubt appreciate not having to remember yet another password! 


Additional Information


--

Minimum Version Requirements


3.96, 4.16

Prerequisites


The 'Third Party Login' feature must be enabled.

Self Configurable


Yes

Business Function


Marketing

BPD Only?


Yes

B2B/B2C/Both


Both

Ballpark Hours From CV (if opting for CV to complete self config component)


Contact Commerce Vision

Ballpark Hours From CV (in addition to any self config required)


0

Third Party Costs


n/a

CMS Category


Feature Management - Third Party Login



Related help