IDHub enables you to manage access, provisioning, and de-provisioning of identities within the enterprise environment and into the Cloud.

  • IDHub synchronizes with trusted sources of user information like LDAP stores or HRMS databases.

  • IDHub runs in a container based environment; docker or Kubernetes, in a single-server or clustered modality.

  • IDHub stores user profile information and historical and transactional data, in its internal database server, acting as an Identity Data Store.

  • IDHub provides administrative and end-user functionalities via a web client interface, using secure communications.

  • The various IDHub modules can be installed per the functionality desired.

Before you install IDHub, please read the previous sections including Self Hosted Deployment Modalities, Self Hosted Requirements, Sizing Your Instance. Also identify the specific modules you are looking to work with.

The following diagrams will illustrate high level architectural scenarios, which you can use to understand deployment options. Please note: these are examples, are not recommended deployment for your production environment, and neither reflect best practices. Please engage with Sath Consulting Services, for help with design specific to your environment.

 - Represents an IDHub Connector.

In this section

Related content

Need more help?

Folks at IDHub are ready to support you.

Ask the IDHub Team

Scenario 1: This is a sample architecture of a self-hosted IDHub as UI front, which connects to Enterprise IDMs, connecting to target systems.


Scenario 2: This is a sample architecture of a self-hosted IDHub as the Identity Management System, which connects to existing infrastructure using SCIM Interface Ports. This scenario also shows the use of separate servers to host the SCIM interface, which in turn, connects to Enterprise systems.


Scenario 3: This is a sample architecture of a self-hosted IDHub, as a Hybrid System with the use of a separate server, connecting to cloud infrastructure, using SCIM Interface Ports, and connecting to existing IDM Infrastructure, using SHIM native API. 

Scenario 4: This is a sample architecture of a self-hosted IDHub, as the Identity Management System on public cloud, connecting to existing infrastructure, using SCIM Interface Ports. This scenario also shows the use of separate servers to host the SCIM Interface, which connects to Enterprise systems.