---
sourceDocument: Australia API Reference
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/api-reference

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia API Reference

ft:clusterId :

    - crapiref

bundleId :

    - crapiref

workflow :

    - Creator


---

# Enable OAuth for Live Connect

# Enable OAuth for Live Connect {#ariaid-title1}

Release version: Australia  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Configure OAuth as an additional authentication method for Live Connect connections. This adds OAuth alongside basic authentication without replacing it.

## Before you begin

* The Live Connect plugin must be installed on your instance. See [Install Live Connect on your ServiceNow instance](https://www.servicenow.com/docs/if_1PWNMECmKCOVELBqpEg "Install Live Connect to enable secure, read-only access to your instance data from external applications.").
* Roles must be assigned to user accounts and ACLs must be configured. See [Assign roles and create service accounts](https://www.servicenow.com/docs/ZVR2lJNhFGgTW5wJ6vIQBw "Assign the sn_odbc_rest_access or sn_jdbc_rest_access role to users who need Live Connect access. You can assign these roles to personal user accounts or create dedicated non-interactive (Machine) service accounts.") and [Create Access Control Lists (ACLs) for Live Connect](https://www.servicenow.com/docs/snYghOPltuehwEcdMSyv5Q "Grant user accounts query access to specific ServiceNow tables through Live Connect using table-level ACLs.").

Role required: admin

## About this task

Basic authentication sends a username and password with every request. OAuth provides a token-based alternative, which is stronger and more secure. Configuring OAuth adds it as an available authentication method; it does not
remove or replace basic authentication.

## Procedure

1. Navigate to AllSystem OAuthInbound Integrations.
2. Select New integration.  
   The Select your application connection type dialog opens.
3. Select OAuth - Resource owner password credential grant.
4. On the OAuth configuration form, enter the following information in the Details section:  
   * Name: Enter a unique name for this OAuth configuration (for example, Live Connect OAuth).
   * Provider name: Select the configured provider from the list.
   * Active: This check box is selected by default.

   Note:  
   The Client IDand Client secret values are autogenerated. You will need these values when you configure your Live Connect clients.
5. In the Auth scope section, configure the authorization scope to control which APIs clients can access:  
   * Select an Auth scope from the list.
   * Select the Allow access only to APIs in selected scope check box to restrict client access to only the specified APIs (recommended for security).
6. **Optional:** In the Advanced options section, configure the token lifespans:  
   * Access token lifespan: Set to 1800 seconds (30 minutes) by default. Modify this value if your use case requires a different duration.
   * Refresh token lifespan: Set to 8,640,000 seconds (100 days) by default. Modify this value if your use case requires a different duration.

   These values determine how long tokens remain valid.
7. Select Save.

## Result

Clients configured with the OAuth properties can authenticate to Live Connect using OAuth. Basic authentication remains available for clients that have not been updated. For information about the OAuth properties, see [OAuth connection properties for ODBC and JDBC drivers](https://www.servicenow.com/docs/sVc6NONQeE2Ozf3cfbstFA "Set these properties on the ODBC or JDBC driver to connect to Live Connect using OAuth instead of a username and password.").

*[\>]: and then