Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Overview

This document provides instructions on how to connect to an API to import data from this application into your instance of Zilla.

In this guide, you will:

  1. Launch your application from inside Zilla

  2. Set up an API configuration

  3. Send your data securely to Zilla

Step-by-Step Instructions

This page outlines the process of configuring and using the NetSuite API through Zilla to sync Users, and roles.

Note: Netsuite does not provide an out of the box REST API. A REST API can be created by installing a small piece of software called “RESTlet” in your NetSuite installation. This RESTlet will create the API endpoint required for the API integration. Zilla has built a RESTlet capable of extracting accounts and roles in Netsuite. Please reach out to your Zilla Security contact for additional details.

Summary

Pre-Install

Before the install, you will need to request the RESTLet Javascript Code. You can either speak with your Technical Representative or reach out to support@zillasecurity.com to get the script.

Setup in Netsuite

1. Create a Role

  1. Go to Setup > Users/Roles > Manage Roles > New

  2. Assign the role scopes:

    1. Lists -> Employees

    2. Lists -> Employees Records

    3. Lists -> Subsidiaries

    4. Lists -> Integration Applications

    5. Setup -> REST Web Services

    6. Setup -> Login Using Access Tokens

    7. Setup -> Bulk Manage Login

    8. Setup -> Bulk Manage Roles

    9. Setup -> View Login Audit Roles

  3. Give the role access to all subsidiaries

2. Create a New User

  1. Go to Lists->Employees->Employees->New

  2. Enter a Name and Email

  3. Check GIVE ACCESS in the Access subtab and assign a password to the account

  4. Assign the Role made in the previous step to this user

3. Create an Access Token

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

  2. Generate a Consumer Token assigned to the user you created previously

    1. Store the access secret and token for later use

4. Create an Integration in NetSuite

  1. Go to setup->integration->manage integrations->new create a new Zilla integration

  2. Check 'token based authentication' and 'RESTLets', uncheck 'TBA Authorization Flow' and 'authorization code', then save

  3. Copy Client ID and Secret for later use

Upload Script

  1. Upload the script (Customization->Scripting->Scripts->New).

Note: Make sure all names are the same as the name (ZillaUAR.js) of the file (include the .js). 

  1. Make the created user an owner of the script

  2. check mark "All Employees" to give the user account access to the script

  3. Select Deploy Script

  4. Add the Zilla integration Role to script deployment. Make status 'released'

  5. Copy the External URL that appears once you save it for later use

Setup in Zilla

First, add NetSuite to your applications, then navigate to your NetSuite instance click Sync now in the top right corner and enable API Integration.

Enter all of your information into the corresponding fields in Zilla:

Signature Method: value will be: HMAC-SHA256

Access Token: Token ID from Create a New Access Token Section

Token Secret: Token Secret from Create a New Access Token Section

Consumer Key: Taken from Integration Section

Realm: AccountID value found in the EXTERNAL URL value. For example, if the URL is https://123.restlets.api.netsuite.com … then the Realm value is 123. 

If it’s a sandbox env, the Realm value needs to be 123_SB (with an underscore, not a hyphen). Needs to match the value at end of numbers

Users Endpoint: Taken from the Script Deployment record’s EXTERNAL URL value.

Users Endpoint must contain a complete URL (https://…).

Step 3.

Once the configuration is complete click Update.

Click Next and begin the sync.

Once the sync has been completed all accounts should appear under the Accounts tab.

When you have finished with all the steps above, review the information in Zilla that was synced.

Having trouble? Try our Troubleshooting articles or contact support@zillasecurity.com.

  • No labels