Is this feature disabled?


The Third Party Login feature needs to be switched on for your site by Commerce Vision. Your site also needs to be on 3.96+ (or 4.16+ for linking to existing accounts).

IMPORTANT

The Google Sign In Javascript Platform Library for web documented on this page is being discontinued by Google. The library will be unavailable for download after the March 31, 2023 deprecation date. By default, newly created Client IDs are now blocked from using the older Platform Library, existing Client IDs are unaffected. New Client IDs created before July 29th, 2022 can set `plugin_name` to enable use of the Google Platform Library.


For more information: see: Google Sign In

Google Sign In using the new 'Google Identity Services' will be coming soon. 


Overview

Google's cross-platform sign in is a secure (OAuth 2.0) third party login method for the Web. A Google sign on button can be added to the login modal of your Commerce Vision site so that users can just use their securely authenticated 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. 





On this page:


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/reference

  1. Go to https://console.cloud.google.com/apis/library?pli=1&project=_ and login to your Google account

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

     or 

  3. Use the Search tool to find the 
     
  4. Select the Credentials menu, and the OAuth consent screen tab.

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


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


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

    Google advises as follows regarding JavaScript origins:



  8. 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.00

Prerequisites


'Third Party Login' enabled.

Self Configurable


Yes

Business Function


Website Users

BPD Only?


Yes

B2B/B2C/Both


Both

Third Party Costs


n/a



Related help