UidConsistencyCheckController

Workflow for checking uid-s for duplicates and incorrect length.

UidConsistencyCheckController is the Java-based real-time controller workflow for UID consistency checks. When an entry change in the Identity Store requires a UID consistency verification — for example after a new user is created or a UID-relevant attribute is modified — the Java-based Server creates a request that this controller workflow picks up and passes to the UidConsistencyCheckActivity. The activity verifies that the UID is consistent across all entries and takes corrective action if an inconsistency is detected.

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

UidConsistencyCheckController

Category

Identity Store

Technology

Java-based real-time workflow

LDAP object class

dxmIDMWorkflowDefinition

Workflow type

ProvisionTS

Connected system / controller type

uidConsistencyCheckController

Configuration wizard

LDAP-LDAP

Active in the factory data

FALSE

Factory data version

8.5

Factory data path

Workflows/Default/Identity Store/UidConsistencyCheckController

Prerequisites

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

Workflow and Activities

Activity Type Component description Description Ports

join

UidConsistencyCheckController

UidConsistencyCheckActivity

Activity for uid consistency check

-

Configuration Parameters

Table 1. Workflow parameters of UidConsistencyCheckController
Parameter Default value

timeout

P0Y0M4DT0H0M0S
Table 2. Parameters of activity join
Parameter Default value

domain

cn=My-Company

resourcefamily

UidConsistencyCheck

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 a single activity, UidConsistencyCheckActivity, which uses the uidConsistencyCheckController component to verify and correct UID consistency. There is no error activity and the retrylimit is 0: a request that cannot be processed immediately is not retried and is dropped.

Operation

  1. A change to a UID-relevant entry causes the Java-based Server to create a uidConsistencyCheckController request.

  2. The Java-based Server passes the request to the UidConsistencyCheckActivity.

  3. The uidConsistencyCheckController component checks the UID of the changed entry for consistency across all related entries and corrects any inconsistencies it finds.

  4. Because retrylimit is 0 and there is no error activity, a request that fails is silently dropped without retry or notification.

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