14. Third-party authentication add-on for Google. Customer guide.

The following configuration will allow the customers to configure the Google OAuth application to implement authentication with Google accounts on their LMS sites.

14.1. Integration requisites.

  • It is required to have your LMS site in a domain of your own.

  • Enterprise or performance subscription with the add-on third-party authentication enabled.

14.2. Configuration steps.

14.2.1. Configuration of the Google oauth application.

  1. Log in to your Google account to access The developer's console.

  1. Create an API project for the integration with the LMS site.

  1. Enable the Google +API service.

  1. Go to the OAuth consent screen and configure your app according to the needs and requirements for your initiative. Configuration of the project in the Google console.

  1. On your project, create a set of authorization credentials. Go to The credentials page and define.

  • Authorization type: Web complication.

  • Name: The name of your OAuth 2.0 client. This name is only used to identify the client in the console and will not be shown to end-users.

  1. Set the Redirect Authorized JavaScript origins to https://YOURLMSDOMAIN (without trailing /).

  2. Set the Authorized redirect URIs to https://YOURLMSDOMAIN/auth/complete/google-oauth2/.


14.2.2. Provide eduNEXT with the credentials recently created.

The client ID and client secret can be found at the top-right corner or can be downloaded in a JSON file. Send this information to the eduNEXT support team.


The credentials look like the example below.

  "auth_uri":" https://accounts.google.com/o/oauth2/auth",
  "token_uri":" https://accounts.google.com/o/oauth2/token",
  "auth_provider_x509_cert_url":" https://www.googleapis.com/oauth2/v1/certs",
  "redirect_uris":[" https://YOURLMSDOMAIN/auth/complete/google-oauth2/"]