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:

  1. Install an RCS (either .NET or Java) on your on-prem server.

  2. (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.

  3. Configure Identity Cloud to connect to the RCS.

  4. (Optional) Install and configure the RCS Agent. The RCS Agent acts as a websocket proxy between Identity Cloud and RCS instances.

Read a different version of :