Overview

IDHub connector consists of SCIM and other REST endpoints to perform operations on a target systems. The connectors are developed and maintained independent of mainline IDHub. They are self contained processes running on a server/platform that has direct connection to target systems. Connectors can be run on the Target System Servers.

Connector Framework is the Architecture, Design, Concept, Code, Documentation of connecting IDHub to Target System for Provisioning and Recon.

Operations

  • Create a resource in target systems.
  • Modify a resource in target systems.
  • Remove a resource from target systems.
  • Search All resources from target systems.
  • Search resource from target systems.

A Connector is an instance of the runnable packages and configurations that runs as an independent application that connects IDHub and a Target System. The runnable application for a target system is to be called by its full name Ex. LDAP Connector

Connector Components

Connector Application

A component of the connector that provides SCIM and Recon API and in turn uses a Splice to communicate with target system. Connector Application is a common component for all Connectors

Connector Application Configuration

A configuration file to specify the Autowiring of the splice, authentication information, and any meta data required to communicate with IDHub

Connector Service Provider Interface (SPI)

A set of Java interfaces that becomes a method signature between Connector Application and Splice. See Service Provider Interfaces . The SPI library, jar of interfaces, is a common dependency between Connector Application and Splice.

Splice

A library that implements Connector SPI and talks natively to Target System. A splice implements Connector API. This implementation is loaded by Connector Application using Spring Autowire mechanism.

Splice Configuration

Configuration to be used by a Splice. It will contain metadata to connect to a target system

Null Splice

A splice implementation that does not talk to any Target System, only logs calls. Can be used to as a template to create additional splices

Network Requirements

For v 20.1.0.0

  1. The IDHub must have direct connection to Connector .
  2. The Connector must have direct connection to Target System


Architecture

Projects

Git Location for all Connector Related Projects

https://git.sath.com/idhub-connectors