- Overview
- Supported Connectors
- Adobe Marketing Cloud Connector
- CSV File Connector
- Database Table Connector
- DocuSign Connector
- Google Apps Connector
- Groovy Connector Toolkit
- HubSpot Connector
- Kerberos Connector
- LDAP Connector
- Marketo Connector
- MongoDB Connector
- MS Graph API Java Connector
- PowerShell Connector Toolkit
- Salesforce Connector
- SAP Connector
- Before You Start
- Using the SAP Connector With an SAP HR System
- Using the SAP Connector to Manage SAP Basis System (R/3) Users
- Configuring the SAP Connector For SNC
- Implementation Specifics
- OpenICF Interfaces Implemented by the SAP Connector
- SAP Connector Configuration
- SCIM Connector
- Scripted REST Connector
- Scripted SQL Connector
- ServiceNow Connector
- SSH Connector
- SAP SuccessFactors Connector
- Workday Connector
- Configure Connectors
- Configure Connectors With the Admin UI
- Configure Connectors Over REST
- Connector Reference Properties
- Pool Configuration
- Operation Timeouts
- Connection Configuration
- Synchronization Failure Configuration
- Configure How Results Are Handled
- Specify Which Attributes Are Updated
- Set the Supported Object Types
- Configure Operation Options
- Remote Connectors
- Check External System Status Over REST
- ICF Interfaces
- ICF Operation Options
- Connection Pooling Configuration
- Identity Cloud Glossary
Remote Connectors
In most cases, Identity Cloud bundles the connectors required to connect to remote resources, and assumes that the connector will run on the same host as Identity Cloud. Sometimes, a connector cannot run on the same host as Identity Cloud. This might be for security or network reasons, or because Identity Cloud runs in the cloud while the resource is "on-prem". Connectors that do not run on the same host as Identity Cloud are called remote connectors. To run remotely, a connector needs a remote connector server (RCS), that runs on the same host as the connector. Identity Cloud accesses the connector through the RCS.
Running connectors remotely requires the following high-level steps:
Install an RCS (either .NET or Java) on your on-prem server.
(Optional) Many connectors are bundled with the RCS itself. If the connector you want to use is not bundled with the RCS, download it from the early access download site, and put the .jar file or .dll file on your remote server, in the
/path/to/openicf/connectors/directory.(Optional) Install and configure the RCS Agent. The RCS Agent acts as a websocket proxy between Identity Cloud and RCS instances.