Google Settings

The application is created and configured using the following link: https://console.cloud.google.com/apis/dashboard.

If no application has been created, then you must click “Create project”, after which the application creation page will open.

If an application has already been created, then to create a new one, you need to click on selecting a project, and then in the window that appears, click the “New project” button, after which the application creation page will open.

In the application creation window that opens, enter the application name “Project name” and then click “Create”.

The application is now created. You need to configure it; to do this, go to the “OAuth consent screen” tab in the “User Type” block, select the “External” type and then click “Create”.

The creation window appears. Fill in the required fields “App name” and “User support email”. Scroll down the page, enter another required field “Email addresses” and click “Save ans continue”.

In the new window, click the "Add or remove scopes" button, a selection window appears on the right.

In the rights selection window, select the rights indicated below, scroll to the end of the page and click “Update”.

After which these rights will appear in the list, scroll to the end of the page and click “Save ans continue”.

If desired, you can add test users, then click “Save ans continue”.

At the final step, a list of all settings will appear, scroll to the end and click “Back to dashboard”.

Go to the "Credentials" tab and click the "Create credentials" button.

Select "OAuth client ID" from the drop-down list.

The creation window appears; in the “Application type” drop-down list, select “Web application”.

After selecting from below, new fields will appear. Fill in the “Name” field, then click “Add url”.

Specify the redirect address from the "Facebook Valid OAuth Redirect URIs" field from the "Redirect for authorization applications via social networks" plugin, changing "fb.callback" to "gg.callback"  (for example, "https://[agent address]/plugin /request/RedirectAuthOtapi/gg.callback" or https://[agent address]/?q=plugin/request/RedirectAuthOtapi/gg.callback), then click "Create".

Important! The site that will be specified will update the "Authorized domains" setting; this domain will be displayed to the user when logging in. In order for the name and logo to be shown, you need to upload the logo at the creation stage in the "OAuth consent screen" (or change it after creating the application by clicking "Edit app") and go through the confirmation stage from Google (confirmation takes 2-3 days, you need to prove that this application actually belongs to the person who creates it).

After which a window with data will appear, the fields “Client ID” and “Client secret” will be needed for configuration in the OT admin panel, after which we click “OK”.

This client will appear in the list; if “Client ID” and “Client secret” were not saved previously, they can be seen again by clicking the edit button.

Go to the "OAuth consent screen" tab, click "Publish app".

A consent window appears, click “Confirm”.

After which we can see that the status has changed to “In production”.

OT admin settings

Open the “Plugins” section in the admin panel.

We check the presence of the plugin “Redirect for authorization applications via social media”. networks" (RedirectAuthOtapi) - it will help you work with Google. We'll definitely activate it. If it is not on the list, contact support.

If the plugin is not active, then click on the gear in the “Actions” column and activate it

Go to the plugin “Redirect for authorization applications via social networks”. Let's create Google. Click on the “+” button and in the first line “External authentication system” select Google. “Application Type” select “Website”.

For the created settings, in the “Social network application ID” field, enter “Client ID”; in the “Social network application secret” enter “Client secret”. In the "Redirect Address" field, enter the redirect address from the "Facebook Valid OAuth Redirect URIs" field from the "Redirect for authorization applications via social networks" plugin, changing "fb.callback" to "gg.callback" (for example, "https:// [agent address]/plugin/request/RedirectAuthOtapi/gg.callback" or https://[agent address]/?q=plugin/request/RedirectAuthOtapi/gg.callback) (the same URL was previously specified in the Authorized redirect URLs settings) .





  • Нет меток