Implementing IdentityNow Custom Connectors

This document describes how to create a custom connector using SailPoint’s OpenConnector framework.

IdentityNow includes many connectors through which it can connect to external systems, both to read account and entitlement information and to process account provisioning requests. Occasionally, however, there may be a need to create a custom connector to connect to an application for which IdentityNow does not have a built-in connector.

Unless direct provisioning is required, custom connectors are seldom necessary because user data is generally available through files, database connections, etc. IdentityNow’s built-in connectors can consume data from delimited file extracts, database connections (JDBC), and web-services (REST), just to name a few. Even in cases where the data extract is not in a readily digestible format, there are configurations provided with these available connectors can parse or otherwise pre-process the data to prepare it for recording in IdentityNow; the developer writing the rules must, of course, be familiar with file parsing in Java. However, when provisioning is required or if these built-in features do not meet the business need, writing a custom connector using the open connector framework is a good option.

SailPoint strongly encourages both partners and customers alike to purchase SailPoint Expert Services hours to assist in these development activities. These deep level implementations are powerful, but also complex to do successful without proper experience. In addition, custom connectors are not covered by SailPoint Support. Any deployment of custom code is your own responsibility to create and maintain.

New in 2023! Use the new SDK/CLI to develop connectors to SaaS systems. For more information, refer to SaaS Connectivity.