Set up a NetSuite connector

ConductorOne provides identity governance for Oracle NetSuite. Integrate your NetSuite instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests.

Capabilities

Resource	Sync	Provision
Accounts
Roles

The NetSuite connector supports automatic account provisioning.

This connector does not support account deprovisioning. You must deprovision accounts directly in NetSuite.

Gather NetSuite credentials

Configuring the connector requires you to pass in credentials generated in NetSuite. Gather these credentials before you move on.

A user with an Administrator role in NetSuite must perform this task.

Before you begin: Make sure you have enabled the following features for your NetSuite instance:

• Token-Based Authentication
• REST Web Services
• Suite Analytics Workbook

You’ll find directions for enabling features in the NetSuite documentation.

Locate your NetSuite Account ID

1. In NetSuite, navigate to Setup > Company > Company Information.

2. Find the ACCOUNT ID field on the page. Make a note of your account ID. We’ll use it in Step 5.

Generate a consumer key and consumer secret

1. In NetSuite, navigate to Setup > Integrations > Manage Integrations. Click New to create a new integration.

2. Give the new integration a name, such as “ConductorOne”.

3. Check the box for TOKEN-BASED AUTHENTICATION.

4. Click Save. The new integration is created, and its consumer key and consumer secret are shown.

5. Make a careful note of these credentials (they won’t be shown again).

Create a NetSuite role and add it to a user

1. Still in NetSuite, navigate to Setup > Users/Roles > Manage Roles. Click New to create a new role.

2. Give the new role a name, such as “ConductorOne integration”.

3. Assign the following permissions to the role:

   • Setup - REST Web Services
   • Setup - Log in using Access Tokens
   • Setup - Bulk Manage Roles
   • Reports- Suite Analytics Workbook
   • Lists - Employee Record
   • Lists - Employees

   Why are these permissions needed? The integration uses these permissions to read and query SuiteQL tables containing information on roles and employees.

4. Click Save.

5. Next, assign the new role to a user. You might want to create a new user for this purpose rather than assigning the role to an existing user. Navigate to Lists > Employees > Employees, then search for the employee by email.

6. Click Edit next to the name of the employee you want to assign a role to.

7. Click the Access subtab.

8. In the Role field, select a role for this employee.

9. Click Add.

10. Click Save.

Generate a token key and token secret

1. In NetSuite, navigate to Setup > Users/Roles > Access Tokens. Click New to create a new token.

2. Select the application (integration), role, and user you created in the previous steps, and give the token a name.

3. Click Save. The new token is created, and its key and secret are shown.

4. Make a careful note of these credentials (they won’t be shown again).

That’s it! Next, move on to the connector configuration instructions.

Configure the NetSuite connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of NetSuite credentials generated by following the instructions above

Cloud-hosted

Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.

1. In ConductorOne, navigate to Admin > Connectors and click Add connector.

2. Search for NetSuite and click Add.

3. Choose how to set up the new NetSuite connector:

   • Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)

   • Add the connector to a managed app (select from the list of existing managed apps)

   • Create a new managed app

4. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.

   If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.

5. Click Next.

6. Find the Settings area of the page and click Edit.

7. In the Account ID field, enter the NetSuite domain.

8. In the Consumer key and Consumer secret fields, enter the credentials you generated.

9. In the Token key and Token secret fields, enter the credentials you generated.

10. Click Save.

11. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

That’s it! Your NetSuite connector is now pulling access data into ConductorOne.

Self-hosted

Follow these instructions to use the NetSuite connector, hosted and run in your own environment. Contact ConductorOne’s support team to download the latest version of the connector.

When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.

Step 1: Set up a new NetSuite connector

1. In ConductorOne, navigate to Connectors > Add connector.

2. Search for Baton and click Add.

3. Choose how to set up the new NetSuite connector:

   • Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)

   • Add the connector to a managed app (select from the list of existing managed apps)

   • Create a new managed app

4. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.

   If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.

5. Click Next.

6. In the Settings area of the page, click Edit.

7. Click Rotate to generate a new Client ID and Secret.

   Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your NetSuite connector deployment:

Secrets configuration

# baton-netsuite-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-netsuite-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # NetSuite credentials
  BATON_ACCOUNT_ID: <NetSuite account ID>
  BATON_CONSUMER_KEY: <NetSuite consumer key>
  BATON_CONSUMER_SECRET: <NetSuite consumer secret>
  BATON_TOKEN_KEY: <NetSuite token key>
  BATON_TOKEN_SECRET: <NetSuite token secret>

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-netsuite.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-netsuite
  labels:
    app: baton-netsuite
spec:
  selector:
    matchLabels:
      app: baton-netsuite
  template:
    metadata:
      labels:
        app: baton-netsuite
        baton: true
        baton-app: netsuite
    spec:
      containers:
      - name: baton-netsuite
        image: ghcr.io/conductorone/baton-netsuite:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-netsuite
        envFrom:
        - secretRef:
            name: baton-netsuite-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files.

2. Check that the connector data uploaded correctly. In ConductorOne, click Applications. On the Managed apps tab, locate and click the name of the application you added the NetSuite connector to. NetSuite data should be found on the Entitlements and Accounts tabs.

That’s it! Your NetSuite connector is now pulling access data into ConductorOne.