RiskGvnController
Sample workflow for risk governance.
RiskGvnController is the Java-based real-time controller workflow for risk governance. When a
risk-relevant object in the Identity Store changes — such as an assignment or a role — the Java-
based Server creates a request that this controller workflow picks up and delegates to the
RiskGovernanceActivity. The activity evaluates and updates the risk values for affected users
and objects, ensuring that risk levels remain current after each change.
The workflows in this reference are delivered as factory data and are loaded into the Connectivity configuration database during the initial configuration. They are samples: use the Identity Manager to copy a workflow into your own scenario and adapt the copy. Do not change the delivered objects, because a product update can replace them.
At a Glance
Name |
|
Category |
Identity Store |
Technology |
Java-based real-time workflow |
LDAP object class |
|
Workflow type |
|
Connected system / controller type |
|
Configuration wizard |
|
Active in the factory data |
FALSE |
Factory data version |
8.5 |
Factory data path |
|
Workflow and Activities
| Activity | Type | Component description | Description | Ports |
|---|---|---|---|---|
|
|
|
Error Activity |
|
|
|
|
Activity for risk calculation |
- |
Ports
| Activity | Port | Component description | Connector | Connected directory | Bind profile | SSL |
|---|---|---|---|---|---|---|
|
|
|
|
- |
- |
not set |
Configuration Parameters
| Parameter | Default value |
|---|---|
|
P0Y0M4DT0H0M0S |
| Parameter | Default value |
|---|---|
|
LDAP |
|
3 |
|
P0Y0M1DT0H0M0S |
|
P0Y0M0DT2H0M0S |
| Parameter | Default value |
|---|---|
|
dxmPassword |
| Parameter | Default value |
|---|---|
|
cn=My-Company |
|
RiskGovernance |
|
0 |
|
P0Y0M1DT0H0M0S |
|
P0Y0M0DT0H30M0S |
A Java-based real-time workflow runs as a permanently loaded configuration in the Java-based Server (IdS-J). It is triggered by a request or an event rather than by a schedule. Each workflow consists of activities; an activity opens one port per system it talks to, and each port uses a connector to reach that system.
Most provisioning workflows contain a join activity that performs the actual work and an error
activity that receives requests which still fail after all retries and sends a notification about
them. The retrylimit, waitbeforeretry and timeout parameters of an activity control how often
and how long a failed request is retried before it is handed to the error activity.
The event port publishes change events over JMS, and the notify port sends e-mail notifications.
Neither port is bound to a connected directory.
The workflow has two activities. The RiskGovernanceActivity uses the RiskGovernanceController
component to evaluate and update risk values in response to each incoming request. The
retrylimit is 0, meaning requests that fail are not retried; the error activity handles
failures by sending an e-mail notification through the Message port.
Operation
-
A change to a risk-relevant object (for example an assignment or role) causes the Java-based Server to create a
riskControllerrequest. -
The Java-based Server passes the request to the
RiskGovernanceActivityof this workflow. -
The
RiskGovernanceControllercomponent evaluates the risk model and updates the risk values for the affected users and objects. -
Because
retrylimitis0, a request that fails is immediately forwarded to theerroractivity for e-mail notification; no automatic retry occurs. -
The workflow is delivered inactive (
dxmActiveisFALSE). Copy it into your own scenario and activate the copy.