X

The Integration blog covers the latest in product updates, best practices, customer stories, and more.

Oracle Integration - Connecting to NetSuite using Token Based Authentication

In this blog, We shall talk about Token Based Authentication(TBA) which is one of the security policies supported by NetSuite adapter in Oracle Integration.

If you want to use token-based authentication with the Oracle NetSuite Adapter, You should have the following information that is required for creating a connection.

  • Consumer key
  • Consumer secret
  • Token
  • Token secret
  • Account ID

And to use Token Based Authentication (TBA), you need to complete the tasks given below in the NetSuite application.

  1. Enable Token-Based Authentication
  2. Create Integration record
  3. Create a Role and assign to a User
  4. Create an Access Token for the Integration record, User, and Role
  5. NetSuite Account ID.

Let us go through the below steps and get the values required for us to create a connection using NetSuite adapter in Oracle Integration.

1. Enable Token-Based Authentication

Go to Setup in NetSuite application > Company > Enable Features > Click the SuiteCloud subtab --> Under Manage Authentication section, check the TOKEN-BASED AUTHENTICATION (Please note that the features Client SuiteScript and Server SuiteScript must also be enabled to use token-based authentication with RESTlets, If it is not enabled, please enable).

2. Create Integration record

Click:

  1. Setup
  2. Integration
  3. Manage Integrations
  4. New
  • Enter “OIC INTEGRATION TBA” as the name of the integration. Adding a description is optional.
  • Ensure, the "State" is enabled
  • Select TOKEN-BASED AUTHENTICATION and uncheck the "TBA: AUTHORIZATION FLOW" and "AUTHORIZATION CODE GRANT" option, and check the "TBA: ISSUETOKEN ENDPOINT"  option. 
  • Click Save

Please make a note of CONSUMER KEY, CONSUMER SECRET. Please note that you can see this information upon saving the Integration Record. If you miss to note Consumer Key, Consumer Secret then you can edit the Integration Record and click on Reset Credentials to view Consumer key and Consumer Secret.

3. Create a Role and assign to a User

Please use an existing account that will remain active on an ongoing basis. This way you do not need to consume an open user account license

OR

If you want to create a new role, look at the steps given below:

Navigate to Setup > User/Roles > Manage Roles > New and create a new role called OIC Sync Role (or any other name you prefer)  > Click on Permissions tab and provide permission and access levels to the each and every object which you want to access as part of the integration

The role must have "User Access Tokens" permission for integration using TBA

And then create a new user or use existing user and add above role to the user.

4. Create an Access Token for the Integration record, User, and Role

Click on 

  1. Setup
  2. Users/Roles
  3. Access Tokens
  4. New
  • From the drop down in the APPLICATION NAME, select the OIC INTEGRATION TBA Integration created in previous steps
  • From the drop down select the User Account that will be used for the integration.
  • Enter the Role of the user.
  • The Token Name will be populated.
  • Click Save. Access Token is CreatedThe Token ID and Token Secret will be generated. Please copy the values

5. NetSuite Account ID

   You can find your NetSuite account ID at the beginning of the NetSuite URL. For example, if the URL is https://1234567.app.netsuite.com/, your account ID is 1234567

Finally, you can create a connection using NetSuite adapter in Oracle Integration and provide all the values you have got as part of this blog and use NetSuite connection to invoke your NetSuite application from Oracle Integration.

Graphical user interface, application, Teams

Description automatically generated

Refer NetSuite documentation for more information and refer Oracle Integration to get more details of the NetSuite Adapter.

For more information, please visit Oracle docs

Refer my other blogs

 

 

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.