MarkAffectedUsers

Sample workflow for finding and flagging the users affected by privilege changes. Checks for TBA flagged groups, permissions and roles and marks the affected users with TBA.

MarkAffectedUsers scans groups, permissions and roles that are flagged for recalculation (TBA — "to be assigned") and marks each user who holds one of those items as also pending a privilege update. This is a preparatory step: once the affected users are marked, the UserResolution or PrivilegeResolution workflow can pick them up and recalculate their privileges.

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

MarkAffectedUsers

Prerequisites

Copy the workflow into your scenario and activate it 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`	`PrivilegeResolutionController`	`PrivilegeResolutionActivity`	Activity for user resolution and account update.	-

error

provisioningActivity

Error Activity

Message

join

PrivilegeResolutionController

PrivilegeResolutionActivity

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 `MarkAffectedUsers`
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
`resourcefamily`	ConsistencyCheck
`retrylimit`	3
`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 PrivilegeResolutionActivity component to scan for TBA-flagged groups, permissions and roles and mark the affected users. 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 change to a group, permission or role sets its TBA flag, which triggers a request for a dxrUser controller type in the Java-based Server.
The Java-based Server passes the request to the join activity of this workflow.
The PrivilegeResolutionActivity component scans the TBA-flagged objects and identifies the users who hold them.
Each identified user is flagged as pending a privilege update (TBA) so that the subsequent privilege resolution run can process them.
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 and activate the copy.