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

RiskGvnController

Category

Identity Store

Technology

Java-based real-time workflow

LDAP object class

dxmIDMWorkflowDefinition

Workflow type

ProvisionTS

Connected system / controller type

riskController

Configuration wizard

LDAP-LDAP

Active in the factory data

FALSE

Factory data version

8.5

Factory data path

Workflows/Default/Identity Store/RiskGvnController

Prerequisites

  • Copy the workflow into your scenario and activate it in the Java-based Server.

Workflow and Activities

Activity Type Component description Description Ports

error

error

provisioningActivity

Error Activity

Message

join

RiskGovernanceController

RiskGovernanceActivity

Activity for risk calculation

-

Ports

Activity Port Component description Connector Connected directory Bind profile SSL

error

Message

errorPort

ErrorNotifyMailConnector

-

-

not set

Configuration Parameters

Table 1. Workflow parameters of RiskGvnController
Parameter Default value

timeout

P0Y0M4DT0H0M0S

Table 2. Parameters of activity error
Parameter Default value

resourcefamily

LDAP

retrylimit

3

timeout

P0Y0M1DT0H0M0S

waitbeforeretry

P0Y0M0DT2H0M0S

Table 3. Parameters of port Message (activity error)
Parameter Default value

decrypt.attribute

dxmPassword

Table 4. Parameters of activity join
Parameter Default value

domain

cn=My-Company

resourcefamily

RiskGovernance

retrylimit

0

timeout

P0Y0M1DT0H0M0S

waitbeforeretry

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

  1. A change to a risk-relevant object (for example an assignment or role) causes the Java-based Server to create a riskController request.

  2. The Java-based Server passes the request to the RiskGovernanceActivity of this workflow.

  3. The RiskGovernanceController component evaluates the risk model and updates the risk values for the affected users and objects.

  4. Because retrylimit is 0, a request that fails is immediately forwarded to the error activity for e-mail notification; no automatic retry occurs.

  5. The workflow is delivered inactive (dxmActive is FALSE). Copy it into your own scenario and activate the copy.