Skip to content

Connecting SailPoint and Oracle NetSuite SaaS

To connect SailPoint with Oracle NetSuite, perform the following tasks:

Adding the Source in SailPoint

To connect to SailPoint, perform the following steps. Once the connection is made, you can configure it to meet your company's needs.

Important

By default, the provisioning feature is disabled, and the connector only supports read-only operations. To support provisioning operations, you must manually enable the feature in the source configuration.

To configure a new source:

  1. Sign in to SailPoint.
  2. Go to Admin > Connections > Sources.
  3. Select Create New.
  4. Search for the connector by entering the name in the search box, and then select Actions.

  5. In the Actions dropdown list, select the setup method:

    • Express Setup - Quickly create a read-only connection to your target system by providing minimal configurations and authentication. On completion, aggregation is automatically started.

      Note

      Express Setup supports Credential Providers. For information on supported credential providers and configuration, refer to Credential Providers. For more information, contact your SailPoint Customer Service Manager.

    • Standard Setup - Provide detailed basic configuration to create the source. Once the source is created, continue with source setup.

Configuring a Source Using Express Setup

Express Setup minimizes the initial configuration process so you can quickly connect the application and immediately begin aggregating user account and entitlement data.

  1. Review the directions and select Start Express Setup.

  2. Review the pre-populated Source Name, Source Owner, and Description. To update, select Edit.

    Note

    The source name must be unique. You can change these settings later in the source configuration.

  3. (Optional) If enabled for your organization, select the Use a Credential Provider checkbox to manage the source's authentication using a credential provider.

    Note

    To add a Credential Provider in SailPoint, go to Admin > Connections > Credential Providers. For more information about credential providers, refer to Credential Providers.

  4. Configure the authentication to allow SailPoint to connect to the source. For more information, refer to the Connection Settings section.

  5. Select Finish.

    After a successful test connection, the system creates your source and prompts you to run an aggregation.

    • If you want to aggregate now, select Aggregate.

      • To see the latest account aggregation history, go to Account Management > Account Aggregation.
      • To see the list of aggregated source accounts, go to Account Management > Accounts.

    • If you want to aggregate later, select Exit. This returns you to the Sources page. Your new source is listed, but contains no accounts or aggregation history yet.

Configuring a Source Using Standard Setup

Use Standard Setup to configure the connector for full feature support.

  1. In the Source Name field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters.
  2. In the Description field, provide additional details about the source to help distinguish it from similar sources. This field allows a maximum of 2,000 characters.
  3. In the Source Owner field, begin typing the name of an owner. Matches appear after you type two or more letters. For more information, refer to Assigning a Source Owner.
  4. (Optional) Select a governance group to grant its members source or role sub-admin level oversight of the source and its access. For more information, refer to Creating and Managing Governance Groups.
  5. If this source represents a primary system containing your organization's personnel records, select the Authoritative Source checkbox. For more information, refer to Creating Identity Profiles.
  6. Select Continue. The source is created, and you are navigated to the Source Setup > Base Configuration page. Continue to configure your connected source there.

Base Configuration

Provide the base configuration parameters. Information you entered in the Create New Source dialog is automatically entered into the fields in the Base Configuration page. You can edit this information if necessary.

  1. Enter a unique name and description for the source.

  2. In the Source Owner dropdown list, select the identity that owns this source.

    • To find a source owner, begin entering their name.

  3. (Optional) If enabled for your organization, select the Use a Credential Provider checkbox to manage the source's authentication using a credential provider.

    Note

    To add a credential provider, go to Admin > Connections > Credential Providers. For more information about credential providers, refer to Credential Providers.

  4. Configure the authentication to allow SailPoint to connect to the source. Refer to Connection Settings for more information.

  5. (Optional) In the Governance Group for Source Management dropdown list, select a governance group to associate with this source. For more information about governance groups, refer to Associating Governance Groups with a Source.

  6. (Optional) Choose whether to enable or disable provisioning for the source. Provisioning is disabled by default.

    • Enable Provisioning - Set the toggle to Enabled to allow the source to create, update, and deactivate accounts in the connected source system.

    • Disable Provisioning - Set the toggle to Disabled to disable provisioning for the source. Disabling provisioning will prevent the creation, updating, or deactivating of accounts on this source.

  7. Select Save.

Connection Settings

The following information is required to connect and interact with Oracle NetSuite SaaS.

Screenshot

Connection Settings

  1. Enter the Account ID assigned to your organization by the Oracle NetSuite system.

Authentication Settings

This connector supports Token Based Authentication.

Screenshot

Authentication Settings

  1. Enter the Client ID and Client Secret of an integration record generated by the Oracle NetSuite system during setup.
  2. Enter the Token ID and Token Secret generated for the access token.
  3. Enter the Application ID that is the unique identifier generated by Oracle NetSuite system during the setup process when an external application is required to be integrated.

Page Size

Screenshot

Page Size

  1. In the Page Size field, enter the number of records to aggregate in a single page when iterating over large datasets. The default size is 50.
  2. Select Save.

Additional Settings

This connector supports the read operation of additional attributes by configuring the attribute XPath in Attribute Mapping and adding the attribute to account schema.

Attribute Mapping

Screenshot

Attribute Mapping

To add an additional attribute:

  1. Enter the attribute's name in Schema Attribute.

  2. Enter the attribute's XPath in XML XPath / CustomAttribute.

    The XPath must be given by considering /record as the root element in the XML response.

    For example, this is the SOAP response for employee:

    Example 
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header>
<platformMsgs:documentInfo xmlns:platformMsgs="urn:messages_2019_1.platform.webservices.netsuite.com">
<platformMsgs:nsId>WEBSERVICES_TSTDRV942460_0920202136479827402549852_32553d3a7</platformMsgs:nsId>
</platformMsgs:documentInfo>
</soapenv:Header>
<soapenv:Body>
<getResponse xmlns="urn:messages_2019_1.platform.webservices.netsuite.com">
<readResponse>
<platformCore:status isSuccess="true" xmlns:platformCore="urn:core_2019_1.platform.webservices.netsuite.com"/>
<record internalId="901077" xsi:type="listEmp:Employee" xmlns:listEmp="urn:employees_2019_1.lists.webservices.netsuite.com">
<listEmp:entityId>Testing XPath</listEmp:entityId>
<listEmp:firstName>Testing</listEmp:firstName>
<listEmp:lastName>XPath</listEmp:lastName>
<listEmp:isInactive>false</listEmp:isInactive>
<listEmp:lastModifiedDate>2021-09-20T00:46:59.000-07:00</listEmp:lastModifiedDate>
<listEmp:dateCreated>2021-09-20T00:46:59.000-07:00</listEmp:dateCreated>
<listEmp:initials>TX</listEmp:initials>
<listEmp:department internalId="1" xmlns:platformCore="urn:core_2019_1.platform.webservices.netsuite.com">
<platformCore:name>Admin</platformCore:name>
</listEmp:department>
<listEmp:globalSubscriptionStatus>_softOptIn</listEmp:globalSubscriptionStatus>
<listEmp:payFrequency>_everyTwoWeeks</listEmp:payFrequency>
<listEmp:useTimeData>_wage</listEmp:useTimeData>
<listEmp:usePerquest>false</listEmp:usePerquest>
<listEmp:isSalesRep>true</listEmp:isSalesRep>
<listEmp:isSupportRep>false</listEmp:isSupportRep>
<listEmp:hireDate>2021-09-20T00:00:00.000-07:00</listEmp:hireDate>
<listEmp:gender>_omitted</listEmp:gender>
<listEmp:giveAccess>false</listEmp:giveAccess>
<listEmp:defaultExpenseReportCurrency internalId="1" xmlns:platformCore="urn:core_2019_1.platform.webservices.netsuite.com">
<platformCore:name>USA</platformCore:name>
</listEmp:defaultExpenseReportCurrency>
<listEmp:sendEmail>false</listEmp:sendEmail>
<listEmp:requirePwdChange>false</listEmp:requirePwdChange>
<listEmp:commissionPaymentPreference>_systemPreference</listEmp:commissionPaymentPreference>
<listEmp:eligibleForCommission>true</listEmp:eligibleForCommission>
<listEmp:currencyList>
<listEmp:employeeCurrency>
<listEmp:currency internalId="1" xmlns:platformCore="urn:core_2019_1.platform.webservices.netsuite.com">
<platformCore:name>USA</platformCore:name>
</listEmp:currency>
</listEmp:employeeCurrency>
</listEmp:currencyList>
<listEmp:customFieldList xmlns:platformCore="urn:core_2019_1.platform.webservices.netsuite.com">
<platformCore:customField internalId="52" scriptId="custentity417" xsi:type="platformCore:BooleanCustomFieldRef">
<platformCore:value>false</platformCore:value>
</platformCore:customField>
<platformCore:customField internalId="34" scriptId="custentity400" xsi:type="platformCore:BooleanCustomFieldRef">
<platformCore:value>false</platformCore:value>
</platformCore:customField>
</listEmp:customFieldList>
</record>
</readResponse>
</getResponse>
</soapenv:Body>
</soapenv:Envelope>

    The XPath entry will be as follows:

    Schema Attributes Navigation Path (XML XPath) / Custom Attribute
    firstName listEmp:firstName
    department listEmp:department/platformCore:name

  3. Select Add Another to configure additional attributes.

  4. Select Save.

Custom Attributes

This connector can be configured to read and write custom attributes. Add the custom attribute name to the account schema, then add the customAttribute using the REST API.

Note

For more information on SailPoint's REST APIs, refer to Best Practices: REST API Authentication and REST API - Update Source (Partial) in the SailPoint Developer Community.

The following Oracle NetSuite Custom field types are supported:

  • Checkbox
  • Date
  • Free-Form Text
  • Email Address
  • Phone Number
  • Hyperlink

To add the custom attribute label (case sensitive) in the schema, select the Add New Attribute button.

You can find custom attribute labels by going to Customization > Lists, Records, & Fields > Entity Fields in the Oracle NetSuite managed system.

Schema Attributes Navigation Path (XML XPath) / Custom Attribute
Custom_Sales CustomAttribute
Custom_InventoryId CustomAttribute

Review and Test

Perform a test to confirm the connection to SailPoint.

  1. Go to Review and Test.

  2. Confirm that the entries in each field are correct.

    If you note any mistakes, return to the section and make corrections.

  3. Select Test Connection.

SailPoint Application Onboarding

SailPoint application onboarding enables you to easily onboard new applications and create sources following the successful onboarding of a discovery source. To use this feature, continue to Discovered Applications in the SailPoint user interface.

For more information, refer to Application Onboarding in the SailPoint SaaS documentation.

Documentation Feedback

Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.