---
sourceDocument: Australia Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Configure OAuth authorization code flow

# Configure OAuth authorization code flow for Zero Copy Connector for ERP {#ariaid-title1}

Release version: Australia  
Updated October 22, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Configure OAuth authorization code flow for SAP and use OAuth to authenticate and authorize users for OData endpoints.

## Before you begin

Note:  
The OAuth authorization code flow can be used to call OData endpoints (create, read, and update). Currently, OAuth can't be used for tables, BAPI, or RFC.

To understand OAuth, see [Set up OAuth](https://www.servicenow.com/docs/access?context=t_SettingUpOAuth&version=australia&pubname=australia-platform-security&ft:locale=en-US) and [OAuth Inbound](https://www.servicenow.com/docs/access?context=oauth-inbound&version=australia&pubname=australia-platform-security&ft:locale=en-US).  
Consult with your SAP administrator:

* Obtain the client ID and client secret. You need this information for the application registry form.
* Ask whether the refresh token is a one-time usable token. A scheduled job that retrieves information from SAP runs once per day. If you need to run the scheduled job more often or on demand, discuss the access token and refresh token options. For more information, see [Manage OAuth tokens](https://www.servicenow.com/docs/access?context=t_ManageTokens&version=australia&pubname=australia-platform-security&ft:locale=en-US).
* Ask them to enable the gateway services to expose the OData endpoints to use.
* Ask them to create a scope in SAP for the exposed OData endpoints and give you the name and OAuth scope. You need this to configure the scope on the application registry form.
{#configure-oauth-authorization-code-flow-to-use-in-zero-copy-connector-for-erp__ul_ij5_3fh_zfc}

If you have already set up OAuth (for example, with REST through platform features), you can use it in Zero Copy Connector for ERP and skip to step 2 in the procedure.

Role required: sn_erp_integration.erp_admin

## Procedure

1. To set up OAuth, register your application by navigating to AllSystem OAuthApplication Registry.
   1. Select New.
   2. Select Connect to a third party OAuth Provider.  
      Use this form to set SAP as the OAuth provider and ServiceNow as the OAuth client. For detailed information about the fields on this form, see [Connect to a third-party OAuth provider](https://www.servicenow.com/docs/access?context=connect-3rd-party-oauth-provider&version=australia&pubname=australia-platform-security&ft:locale=en-US).
   3. Enter a Name.
   4. Set ServiceNow as the OAuth client by using the information you obtained from your SAP administrator to fill in the Client ID and Client Secret fields.
   5. In Default Grant type, specify how to authenticate SAP.
   6. Unlock the Authorization URL and Token URL fields to enter the URLs.  
   7. Select the OAuth Entity Scopes tab.
   8. Double-click (or use the keyboard shortcut) in the Name and OAuth scope columns to enter the scope information you obtained from your SAP administrator.  
      You can add multiple scopes.

   9. Select Submit.
   {#configure-oauth-authorization-code-flow-to-use-in-zero-copy-connector-for-erp__substeps_xpg_3qh_zfc}
2. Create a credential by navigating to AllConnections \& CredentialsCredentials.
   1. Select New.
   2. Select OAuth 2.0 credentials.  
      For detailed information about the fields on this form, see [OAuth 2.0 credentials](https://www.servicenow.com/docs/access?context=oauth-2-credentials&version=australia&pubname=australia-platform-security&ft:locale=en-US).
   3. Enter a Name.
   4. In OAuth Entity Profile, select sap oauth profile default_profile.
   5. In Integration type, select Personal.  
      In most cases, it is acceptable to use system-based credentials. However, to obtain information from SAP, such as who changed information or details about approval activities, use the personal integration
      type. For more information, see [Using the Personal Authentication dashboard](https://www.servicenow.com/docs/dCeWWAXuTTiyU0uuhpgv5g "Use your personal credentials to connect to third-party integrations. View, authenticate, revoke, and renew your personal authentications through a simplified, consolidated interface.").

   6. Select Submit.
   {#configure-oauth-authorization-code-flow-to-use-in-zero-copy-connector-for-erp__substeps_b4d_d5h_zfc}
3. Add a connection to the correct alias, for example, the following steps use the Zero Copy Connector for ERP HTTP alias.
   1. Navigate to AllConnections \& CredentialsConnections \& Credentials Aliases.
   2. In Name, search for and select Zero Copy Connector for ERP HTTP.
   3. On the Connections tab, select New.  
      For detailed information about the fields on this form, see [Create an HTTP(s) connection](https://www.servicenow.com/docs/access?context=create-https-connection&version=australia&pubname=australia-platform-security&ft:locale=en-US).
   4. Enter a Name.
   5. In Credential, specify the OAuth credential you created in step 2.
   6. Enter the Connection URL.
   7. Select Submit.
   {#configure-oauth-authorization-code-flow-to-use-in-zero-copy-connector-for-erp__substeps_zyb_55h_zfc}

*[\>]: and then