Skip to main content

Change NetSuite connection to token-based authentication (2FA) for 2018.2

Tom Santiago
  • Updated
Follow

Before You Begin

Enable Token-based authentication.

  1. As a NetSuite administrator, log into NetSuite.
  2. Go to Setup > Company > Enable Features.
  3. Click the SuiteCloud subtab.
  4. Scroll down to the Manage Authentication section.
  5. Select the TOKEN-BASED AUTHENTICATION checkbox.
  6. Click Save.

Create custom roles based on the connector you are using.

i) For integrator.io: In NetSuite, go to Setup > Users/Roles > Manage Roles; then click Customize corresponding to the Celigo integrator.io Full Access w/o 2FA[Locked] role and save the role (clone) with a different name.

Notes:

  • "Celigo integrator.io Full Access w/o 2FA[Locked]" is a locked custom Celigo role. When cloning the role, you can add additional permissions to the role to fit your requirements. This role is available in Celigo integrator.io 1.7.4.14 (bundle ID: 20038) and above.
  • When creating custom roles, using alphanumeric characters only.

ii) For eTail connectors: In NetSuite, go to Setup > Users/Roles > Manage Roles; then click Customize corresponding to the Celigo eTail SmartConnectors role and save the role (clone) with a different name.

[A list of eTail connectors: Amazon | BigCommerce | eBay | Magento | Shipwire | Shopify | Walmart | Square]

Notes:

  • "Celigo eTail SmartConnectors" is a locked custom Celigo role. When cloning the role, you can add additional permissions to the role to fit your requirements. This role is available in Celigo integrator.io 1.7.4.14 (bundle ID: 20038) and above.
  • When creating custom roles, using alphanumeric characters only.

iii) For High tech connectors, except for JIRA, CashApp: In NetSuite, go to Setup > Users/Roles > Manage Roles; then click Customize corresponding to the Celigo integrator.io Full Access w/o 2FA[Locked] role and save the role (clone) with a different name.

[A list of High tech connectors: ADP | JIRA | Cash Application Manager | SVB | Vendor Payment Manager | Zendesk ]

Notes:

  • "Celigo integrator.io Full Access w/o 2FA[Locked]" is a locked custom Celigo role. When cloning the role, you can add additional permissions to the role to fit your requirements. This role is available in Celigo integrator.io 1.7.4.14 (bundle ID: 20038) and above.
  • When creating custom roles, using alphanumeric characters only.

iV) For the JIRA connector use the "Celigo JIRA connector" role. For the Cash Application Manager connector, use the "Celigo CashApp Manager SmartConnector" role. The other steps to be performed remain the same as mentioned above.

Note: This article stands true for integrator.io native flows or SmartConnectors. It doesn't apply to V2 SuiteScript flows/ V2 Connectors. Please refer to the respective connector documentation for TBA.

Implement Token-Based Authentication for NetSuite User

As a NetSuite administrator, to implement Token-based authentication for a NetSuite user:

  1. Assign Role to the NetSuite user.
  2. Create Access Tokens for integrator.io.
  3. Update NetSuite connections in integrator.io. An administrator or the NetSuite user to whom the role(s) have been assigned in Step 2 can perform this step.

Step 1 — Assign Role to NetSuite User

As a NetSuite administrator, to assign a role to a NetSuite user:

1. Navigate to Setup > Users/Roles > Manage Users.

2. On the Manage Users page, click on the username for whom you want to implement the Token-based authentication. The Employee page appears.

3. Click Edit.

4. On the Employee page, go to  Access > Roles.

5. Add the custom role that you created in step 2 of the Before You Begin section.

Note: Add the custom roles specific to your connector. The roles are mentioned in detail in the Before You Begin section of this document.

6. Click Save. The confirmation message appears.

Step 2 — Create Access Tokens for integrator.io

As a NetSuite administrator, to create tokens for IO:

1. Go to Setup > Users/Roles > Access Tokens.

2. On the Access Token page, click New Access Token. The Access Token page appears.

3. (IMPORTANT) From the APPLICATION NAME drop-down list box, select the right application based on your connector:

a. Choose eTail Connectors Token-based Auth) for Shopify, Amazon, Amazon Multi-Channel Fulfillment, eBay, Magento 2, BigCommerce, Square, Salesforce Commerce Cloud, and Walmart integration apps.

b. Choose High Tech Connector (Token-based Auth) for ADP, Suitebilling, Zendesk, JIRA, Cash Application Manager (IO), Vendor Payment Manager.

c. Choose Integrator.io (Token-based Auth) for any other custom integration

4. From the USER drop-down list box, click List. A list of users appears and then select the appropriate user.

Note: Make sure you have selected the correct Application Name as mentioned in Step 3 above.

5. From the ROLE drop-down list box, select the custom role you created. The TOKEN NAME populates automatically.

Note: Select roles specific to your connector. The roles are mentioned in detail in the Before You Begin section of this document.

6. Click Save. 

7. Upon save, NetSuite will display the Token Id & Token Secret that you will be required to input in the integrator.io. See the next section.

Note: Token Id and Token Secret are only displayed once & cannot be retrieved again. We recommended that you save them in a password manager application, such as LastPass or store them on your desktop. This way you can reference them later if required.

Step 3 — Update NetSuite Connection with Access Tokens

As a NetSuite administrator or NetSuite user, who has already received the required Roles/Permissions from the NetSuite administrator, you can update an existing NetSuite connection using Tokens in IO:

1. Login to your integrator.io account.

2. Navigate to the Settings page for your NetSuite integration tile. Click on Connections on the left menu.

3. Click the Pencil icon of the NetSuite connection you wish to change from Basic authentication to Token-based Authentication.

4. In the Connection window, enter appropriate details in the text boxes that appear and use the created access tokens in Token Id and Token Secret. For more information, refer to Establish Connections in integrator.io and Field Reference Guide.

Note: You will receive the invalid or missing consumerKey error if you do not select a value from the IClient drop-down list box.

5. (Optional) If you also have Legacy (v2) Integrations that were built in NetSuite, select the Link SuiteScript Integrator checkbox. This will pull your legacy integration data into the integrator.io dashboard.

6. Click the Test button. If you have performed the above steps correctly, the Connection is working fine! message should appear.

7. Click the Save button.

You have now set your integrator.io NetSuite connection to use the Token-based authentication. 

For product-specific details, click on your product and follow the instructions guide:

E-commerce 

Others

CloudExtend Products

Related articles

Comments

0 comments

Please sign in to leave a comment.