Skip to content

Integrating SailPoint with IBM NS1 Connect

IBM NS1 Connect is a premium managed DNS and traffic routing platform built on a global anycast network. It helps enterprises keep their websites and applications fast, resilient, and continuously available. This document provides instructions to configure a new direct connection to an IBM NS1 Connect source. For a reference to the terminology specific to SailPoint products, refer to Source and Connector Definitions.

Note

To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the SaaS Release Notes page.

Supported Features

The IBM NS1 Connect connector supports the following:

Account Management

  • Aggregate Users

Entitlement Management

  • Aggregate Teams

Note

This connector is read-only. It supports test connection, account aggregation, and entitlement aggregation for Quick Compliance. Provisioning, de-provisioning, and write operations are not supported.

Important

Quick Compliance connectors have the following manual aggregation limits within a 24-hour period:

  • Organization Admins: Limited to 3 manual account or entitlement aggregations per day per source. This limit is cumulative across all admins in the organization.
  • Regular Users: Limited to 1 manual account or entitlement aggregation per day per source.

These limits ensure that individual compliance statuses are kept up to date while maintaining continuous compliance monitoring. If you need to run additional aggregations beyond these limits, contact SailPoint Support.

Prerequisites

Before configuring the IBM NS1 Connect connector, ensure the following requirements are met:

  1. Sign in to the IBM NS1 Connect Portal.
  2. Go to User Settings > Users & Teams > API Keys > Create API Key.
  3. Provide a descriptive name for your key.
  4. Select the minimum permissions required for your use case.
  5. Copy and store the generated API key securely.

Note

Once you have generated your API key, you must include it in all API requests by setting it in the X-NSONE-KEY header. For example: curl -X GET "https://api.nsone.net/v1/account/users" \ -H "X-NSONE-Key: your_api_key_here"