Notifications

815 views

Configuring Gmail after Google deprecates OAuth 1.0 authentication 

Overview

Google has deprecated gmail authentication via OAuth 1.0.  

 

Geneva and later

To use a Gmail account in a Geneva or later instance, you can use either password authentication, or OAuth 2.0 authentication.

If OAuth functionality is required for your Gmail integration, you must configure the email acount using OAuth 2.0.  See the product documentation to configure email with OAuth 2.0.

If you want to instead use password authentication, use the Pre-Geneva method described below.

Pre-Geneva

To continue using a Gmail account in an instance prior to Geneva, switch the instance email accounts to use the password authentication method, and configure Gmail for access by the instance.

The password used in the instance depends on whether the Gmail account uses Gmail's 2-Step Verification. This is an authentication method Google uses to enhance email account security. When enabled, a user logging in to the Gmail account must supply additional information, such as a numeric code sent as a text message, in order to complete the log in. If this method is enabled on your Gmail account, the instance cannot respond to the request for additional information, so you must configure the Gmail account to allow the instance to access it.

Option 1: 2-Step Verification Disabled:

  1. Configure the instance SMTP and POP/IMAP Gmail accounts with the primary Gmail username and password credentials.

Option 2: 2-Step Verification Enabled:

  1. In Gmail, create an Application Password dedicated to your ServiceNow instance.
  2. Configure the instance SMTP and POP/IMAP Gmail accounts with the Gmail user name and application password credentials.

For more information see Gmail's 2-Step Verification documentation.

For more information on application-specific passwords, see Gmail's Application Password documentation.

 

Article Information

Last Updated:2016-04-10 10:32:36
Published:2015-01-19