Loading...

Creating an OAuth Application in the Google Cloud Console

Before users can log on to the Web Console by using an existing Google account, you must obtain an application key and application secret from the Google Developers Console. The key and the secret are then used in the OAuth Applications Settings area. For information on the OAuth Applications Settings area and setting up OAuth in SnapProtect, see Adding Application Information for Social Sign In.

Procedure

  1. Create a project for OAuth integration on the Google Developers Console website.

    For information on the Google Developers Console, see Google Developers Console Help.

  2. From the Google Developers Console, go to APIs & auth > Credentials, and in the OAuth section, click Create new Client ID.

    The Create Client ID dialog box is displayed.

  3. Select Web application, and then click Configure consent screen.

    The Consent screen is displayed.

  4. Enter the required information, and then click Save.

    The Create Client ID dialog box is displayed.

  5. In the Authorized Redirect URIs box, enter the URL of the Web Console appended with /oAuthCallback.do. Include the port number in the URL.

    If you have more than one Web Console, enter each URL on a separate line, for example:

    http://client1.mydomain.com:80/webconsole/oAuthCallback.do

    http://client2.mydomain.com:80/webconsole/oAuthCallback.do

    Note: Follow the guidelines Google places on the redirect URI values, for example, "no URL fragments."

  6. Click Save.

    The Client ID for web application screen is displayed.

  7. Record the values for Client ID and Client Secret. These values are required in the setup of OAuth in SnapProtect.

When you set up OAuth in SnapProtect, use the Client ID value as the Application Key and the Client Secret value as the Application Secret.

What to Do Next

Follow the instructions in Adding Application Information for Social Sign In.