Configure Google SMTP using OAuth 2​.0 authentication

If you use the Google SMTP server, AVEVA System Monitor supports OAuth 2.0 authentication. OAuth 2.0 uses token-based authorization instead of a user password.

To use OAuth 2.0, you must first create an OAuth 2.0 Client ID and Client Secret in the Google Cloud Console.

Enable Gmail API and Configure the OAuth Consent Screen

1. Go to https://console.cloud.google.com/ and sign in using the Google account that will be used for SMTP.

2. Select the Project drop-down, select New project, enter the Project name, and select Create.

3. Navigate to APIs & Services > Library.

4. Search for Gmail API, select Gmail API, and then select Enable.

5. Select APIs & Services > OAuth consent screen.

6. In the App Information section, enter the App name and the User support email, and select Next.

7. Set Audience to External, and select Next.

8. In the Contact Information section, enter the required email addresses, and select Next.

9. Select I agree to the Google API Services: User Data Policy, and then select Create.

   The OAuth configuration is created.

10. Once the OAuth client is created. In the left navigation, add the current email address to audience list.

Create OAuth 2.0 Credentials

11. Select APIs & Services > Credentials > Create credentials > OAuth client ID.

12. In Application type drop-down list, select Web application.

13. In the Name field, enter your OAuth 2.0 client name.

    Note: This name is only used to identify the client in the console and will not be shown to end users.

14. Under Authorized redirect URIs, select Add URI and add the following URLs:

    • https://<machinename.domain.com>/systemmonitor/oauth2callback.html

    • https://<machinename.domain.com>/oauth2callback

15. Select Create.

    The Client ID and Client Secret are generated.