This page describes how to use token-based authentication (TBA) using Jitterbit's NetSuite Connector. Prior to configuring TBA in Jitterbit, see Jitterbit's recommendations for enabling TBA in NetSuite.
These instructions assume that you are already using SSO authentication on a NetSuite endpoint and want to change the method of authentication to use TBA. For full documentation on configuring a new TBA or SSO endpoint, see NetSuite Connector Endpoint.
Using the NetSuite Connector is one of several ways to use NetSuite TBA with Harmony. Other options include using a web service method or calling a RESTlet:
- Using NetSuite TBA in a Web Service Method
- Using NetSuite TBA by Calling a RESTlet from a Local File Source
- Using NetSuite TBA by Calling a RESTlet from an HTTP Source or Target
To use the NetSuite Connector to convert an existing NetSuite endpoint configured with SSO authentication to use TBA, follow the steps on this page:
To use TBA with the NetSuite Connector in Jitterbit, these criteria must be met:
- You must have the appropriate permissions role on your NetSuite account.
- You must be using SuiteTalk version 2015.2 or higher.
- You must have TBA enabled for your NetSuite account.
TIP: For additional information, refer to the NetSuite documentation on Getting Started with Token-based Authentication (login to NetSuite required).
Create a Backup
First, you may want to create a Jitterpak to have a backup copy of the project if needed.
Convert to TBA
Open your existing NetSuite endpoint by double-clicking the endpoint in the tree on the left under Connectors > NetSuite > NetSuite Endpoints.
In the configuration, click the button Convert to TBA.
In the popup window, enter the values to be used for Jitterbit to authenticate with your NetSuite instance using TBA. Then click Save.
Account: Enter the NetSuite Account ID associated with your NetSuite account. For instructions on obtaining this value, see Enabling TBA in NetSuite.
Wsdl Download Url: Enter the URL of the NetSuite WSDL used by your existing SSO endpoint. To use TBA, you must be using a version of SuiteTalk that is at least 2015.2. In addition, if you receive an error regarding the data center while testing the connection, the WSDL URL you need to use will be slightly different. For more information, see Data Center Error for SSO or TBA under NetSuite Connector Advanced.NOTE: Initially, it is recommended to use the same WSDL version as your existing SSO endpoint. If you need to upgrade your WSDL, it is recommended to do so separately. This is a recommended step for troubleshooting purposes, so that if you experience issues the cause can be determined.
Jitterbit supports these WSDL versions for TBA:
NOTE: As of January 2018, NetSuite uses the same URL for both their production and sandbox domain. If your NetSuite sandbox has not been refreshed since these changes were implemented, you may need to use a sandbox-specific WSDL URL. For more information, see NetSuite Sandbox WSDL URL under NetSuite Connector Advanced.
https://webservices.netsuite.com/wsdl/v2020_1_0/netsuite.wsdl(supported with agents version 10.18 or higher)
https://webservices.netsuite.com/wsdl/v2019_2_0/netsuite.wsdl(supported with agents version 10.4 or higher)
https://webservices.netsuite.com/wsdl/v2019_1_0/netsuite.wsdl(supported with agents version 10.4 or higher)
https://webservices.netsuite.com/wsdl/v2018_2_0/netsuite.wsdl(WSDL versions 2018.2 and lower are supported with agents version 9.9 or higher)
Consumer Key and Consumer Secret: Enter the NetSuite Consumer Key and Consumer Secret values obtained from NetSuite. For instructions on obtaining these value, see Enabling TBA in NetSuite.
Token Key and Token Secret: Enter the NetSuite Token ID and Token Secret values obtained from NetSuite. For instructions on obtaining these value, see Enabling TBA in NetSuite.CAUTION: If you are using a NetSuite sandbox account, each time the sandbox is refreshed, you will need to create new tokens.
- Signature Algorithm: The Consumer Secret and Token Secret are used to sign the request using either of these supported signature algorithms: HMAC_SHA1 or HMAC_SHA256. These affect how the payload is encrypted and you may select either type.
Call Time Out: Optionally enter the call timeout value in seconds, if you want to the timeout value to be less than the agent setting.NOTE: The default agent setting for timeout of NetSuite calls is 300 seconds.
Test the Endpoint
After your endpoint is created, double-click the endpoint in the tree on the left under Connectors > NetSuite > NetSuite Endpoints.
Then click the Test Connection button to verify the connection to your NetSuite account.
A message will indicate if the connection is successful. If the connection is not successful, make sure you meet the prerequisites and double check the values you provided on this screen. If you receive an error testing the connection, refer to troubleshooting information.
After you have successfully tested your NetSuite TBA endpoint, simply deploy your project to begin using TBA.
Last updated: Jun 08, 2020