EnRole

The EnRole architecture consists of several key components designed to provide a robust identity management solution. The EnRole Server is the central component, responsible for processing user requests, enforcing security policies, and managing user identities. It communicates with the Database, which stores user profiles, roles, permissions, and other configuration data.

Connectors facilitate integration with target systems, such as z/OS, UNIX, and Windows, enabling user provisioning and deprovisioning. The EnRole Server uses a multi-tiered architecture, with a presentation layer (administrative console), a business logic layer (EnRole Server), and a data access layer (database). Communication between components occurs over HTTP/HTTPS, with SOAP used for API interactions.

The database can be DB2 or another supported database. The administrative console provides a GUI for managing users, roles, and policies. Command-line tools are available for automation and advanced configuration.

Compared to competitors, EnRole's architecture is relatively straightforward, focusing on core identity management functions. For example, the `createUser` API call would be processed by the EnRole Server, which would then update the database and trigger the appropriate connector to provision the user's access to the target systems. The system uses RBAC, allowing administrators to define roles and assign permissions to those roles, simplifying access management.