EventBasedUserResolution

Sample workflow for handling an user change event. Resolves the user privileges and / or updates their account attributes.

EventBasedUserResolution reacts to change events published for user entries (dxrUser). It applies both consistency rules and provisioning rules to the changed user, which can trigger account creation, modification or deletion in connected target systems. The ignore, ignoreprefix, include and includeprefix parameters control which attributes of the user entry are considered relevant and passed on for processing; the remaining attributes are skipped so that only meaningful changes drive provisioning actions.

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

EventBasedUserResolution

Prerequisites

The Identity Store domain event policy must be configured to publish events for dxrUser entries.
Both the consistency rules (consistencyrulesroot) and the provisioning rules (provisionrulesroot) must exist in the Identity Store.
Copy the workflow into your scenario, configure tscluster, tsresource, the rule roots and the ignore/include attribute lists, and activate the copy in the Java-based Server.

Workflow and Activities

Activity Type Component description Description Ports

Activity	Type	Component description	Description	Ports
`error`	`error`	`provisioningActivity`	Error Activity	`Message`
`join`	`Server`	`resolutionActivity`	Activity for user resolution and account update.	-

error

provisioningActivity

Error Activity

Message

join

Server

resolutionActivity

Activity for user resolution and account update.

Ports

Activity Port Component description Connector Connected directory Bind profile SSL

Activity	Port	Component description	Connector	Connected directory	Bind profile	SSL
`error`	`Message`	`errorPort`	`ErrorNotifyMailConnector`	-	-	not set

error

Message

errorPort

ErrorNotifyMailConnector

not set

Configuration Parameters

Table 1. Workflow parameters of `EventBasedUserResolution`
Parameter	Default value
`timeout`	P0Y0M4DT0H0M0S
`tscluster`	*
`tsresource`	cn=My-Company

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
`consistencyrulesroot`	cn=domain_name,cn=Rules,cn=Policies,cn=domain_name
`domain`	cn=My-Company
`ignore`	dxmPassword, dxrChallengeResponse, dxrPrivilegesGrantedLink, dxrCreateUserByWF, description
`ignoreprefix`	dxmOpr, dxmPwd, dxrPwd, dxrAssigned, dxrErr, dxrHist, dxrInh, dxrIs
`include`	employeeNumber
`includeprefix`	dxrSec
`provisionrulesroot`	cn=domain_name,cn=Rules,cn=Policies,cn=domain_name
`resourcefamily`	Event_Maintenance
`retrylimit`	3
`sortascending`	TRUE
`sortattribute`	cn
`timeout`	P0Y0M0DT0H15M0S
`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 join activity uses the resolutionActivity component to evaluate the relevance of the changed attributes against the ignore, ignoreprefix, include and includeprefix parameter lists, then applies consistency rules from consistencyrulesroot and provisioning rules from provisionrulesroot. The provisioning rules may generate account changes in connected target systems. Failed requests are retried up to retrylimit (3) times with waitbeforeretry (30 minutes) between attempts; persistent failures are passed to the error activity for e-mail notification through the Message port.

Operation

A client creates, modifies or deletes a user entry in the Identity Store and the event policy publishes a dxrUser change event.
The Java-based Server matches the event against tscluster (*) and tsresource (cn=My-Company) and passes the request to the join activity.
The activity filters the changed attributes through the ignore, ignoreprefix, include and includeprefix lists to determine whether the change is relevant.
For relevant changes the activity applies consistency rules from consistencyrulesroot and evaluates provisioning rules from provisionrulesroot, potentially generating account changes in connected target systems.
Failed requests are retried up to three times; requests that still fail are handed to the error activity for e-mail notification.
The workflow is delivered inactive (dxmActive is FALSE). Copy it into your own scenario, configure the parameters and activate the copy.