Cross Identity Components
  • 25 Jun 2024
  • 1 Minute to read
  • Dark
    Light
  • PDF

Cross Identity Components

  • Dark
    Light
  • PDF

Article summary

Cross Identity is a web application that consists of several components. Some of the components you must install and configure before installing CI. There are some optional components available after installing CI. These optional components provide additional functionalities for the deployment. The following graphic is an overview of the CI components.

Sr. No.

Solution Components

Description

1.

Cross Identity Server (App Server)


This module is the central component of the IDAM solution. It provides both User Interface logic as well as all business processes logic. 

Apache and Tomcat server.

2.

Cache Server Node & Message Queues & Scheduler


CI caches the running data on this cache module. And CI uses the message queues to integrate with various functional modules. The scheduler module manages and maintains the system and batch jobs.

Tomcat for Scheduler and Notification.

Hazelcast Cache and ActiveMQ (for auditing) and RabbitMQ for Connectors.

3.

CI DB Server Node


CI uses the DB Server as the persistent data store for Cross Identity. 

Percona MySQL Cluster (for On-Prem)

4.

CI Agent and IGA/SoT Connectors


CI Server interacts with integrated applications and systems through this agent server. It uses an SoT connector to interact with SoT systems and IGA Connector to interact with applications for provisioning and de-provisioning activities.


Tomcat server.

Cross-Identity Additional Features

Cross Identity installation comprises eight modules. These modules, too, have sub-components that aid in the process. 

  1.  Cross Identity Server is the central component of the IDAM solution. It provides both User logic interface as well as business processes logic.

  2.  CI On-Premise Agent: identifies the connector and forwards the request to the respective connector. 

  3.  CI Application Integration Connectors help to connect Cross Identity and target applications.

  4.  CI Browser Extensions & Thick Client Agent: The browser extension helps you to modify the Cross Identity user interface, and a thick client is a form of client-server architecture.

  5.  CI Custom CP- Gina: allows users to reset and unlock their passwords from the logon screen even when locked out of the system.

  6.  CI WAM Modules: ensure that access to the web application is allowed only when initiated by the Cross Identity. 

  7.  CI RPSA: This process involves changing a password in one of the target systems, such as Windows Active Directory, and then synchronizing all other account passwords for a user in the same password sync group.





Was this article helpful?