Create NetSuite Tokens to be used for Token Based Authentication in the Legacy NetSuite Connector

If you have a Legacy (v2) Celigo Integration, the process for setting up Token-Based Authentication (TBA) is slightly more involved than creating one for integrator.io native Integrations.

To determine if you have Legacy Integrations, look for a grey bar at the top of the Integration tile(s) that says something like “NetSuite - <NetSuite Account ID>”.  The tiles marked with this type of grey bar denote a Legacy Integration.  Tiles without this bar were natively created on the integrator.io platform.  Please refer to the article here for setting up TBA for NetSuite Integrations built natively in integrator.io.

On the Legacy Integration tile, click the “Settings” (gear) icon.

On the of the Integration Settings window, click “Connections”.  Look for a NetSuite connection under the “Type” column.  Click the “Pencil” icon to edit this connection.

This is likely set to an Authentication Type of “Basic”.  To change to TBA, change the Authentication Type to “Token”.

You will now see fields for Consumer Key, Consumer Secret, Token Id and Token Secret.  Please read on for information on how to generate these four keys.

First, you will need to Enable Token-Based Authentication in your NetSuite Environment and either create a new NetSuite role or edit an existing role with the permissions outlined below.  If you're creating a new role, you’ll also need to assign this role to an Employee.

• Enable Token-Based Authentication in your NetSuite environment by browsing to “Setup > Company > Enable Features” and clicking the “SuiteCloud” subtab.  Here, scroll down to the “Manage Authentication” section and check the box next to “TOKEN-BASED AUTHENTICATION".

• Create a new role in NetSuite (Setup > Users/Roles > Manage Roles > New) with an identifiable name, such as “Celigo integrator.io”.  As we cannot create a Token for an Administrator role, a new role will need to be created with the following permissions.

Under Permissions > Transactions:

Under Permissions > Lists:

Under Permissions > Setup:

• Assign this new role to an Employee (Edit the Employee Record, Browse to the Access > Roles Subtab).  Save the changes to the Employee Record.

Next, you will need to create a New Integration.  

• As a NetSuite Administrator, browse to Setup > Integration > Manage Integrations > New.  Here, give the Integration a name. For this example, we’ve named it “Legacy Integrations Connector”.  Be sure to set the State as “Enabled”, if it isn’t already, and check the box under the Authentication Subtab next to “TOKEN-BASED AUTHENTICATION”.  Finally, click the “Save” button to generate your tokens.

• Once you click “Save,” you will be taken to a confirmation page that displays your “CONSUMER KEY” and “CONSUMER SECRET”.  !! IMPORTANT - Be sure to carefully copy and paste the CONSUMER KEY and CONSUMER SECRET into a secure document, such as a LastPass site. You will need these values on hand to Create or Modify your NetSuite Connection in integrator.io.  If these tokens are lost, you will need to generate a new set of tokens to use.  This is the first set of tokens to generate.  Double check that you have copied and pasted them into a document correctly.

Now you will need to create the Token Id and Token Secret.

• Log in as the Employee and switch to the New Role that was assigned (or the role that you modified with the above permissions).

• Click on “Manage Access Tokens” in the Settings Portlet.

• Click “New My Access Token”.

• Under “Application Name *”, select the Name of the Integration you created in the previous steps (e.g. “Legacy Integrations Connector”) then click “Save”.  Note that the “Token Name” field will auto-populate.  You can change this if you wish.

• When you click “Save” in the previous step, you will then be taken to a confirmation screen. !! IMPORTANT - Be sure to carefully copy and paste the TOKEN ID and TOKEN SECRET into a secure document, such as a LastPass site.  You will need these values on hand to Create or Modify your NetSuite Connection in integrator.io.  If these tokens are lost, you will need to generate a new set of tokens to use.

Now that you have all four tokens saved into a document, you’re ready to plug them into the Legacy NetSuite connection.

In the integrator.io Legacy NetSuite Connection, fill in the Consumer Key, Consumer Secret, Token Id, and Token Secret with the values you have generated in the previous steps.  Click the “Test” button to test the connection and to double-check that the values have been copied to the correct fields.  If everything was done correctly, you should get a “Connection is working fine!” message. Click the “Save” button.

Once saved, your Legacy NetSuite connection will now be using Token-Based Authentication.