LDAP2Ident_Validation
Workflow for Validation between LDAP and MetaRole
A validation workflow compares the content of the connected system with the state that DirX Identity
holds for the corresponding target system. It runs in one of two modes, controlled by the mode
parameter of the workflow:
-
InitialLoad - exports all accounts and groups and their relationships from the connected system and imports them into the target system subtree of the Identity Store in replace mode. Use this mode when you take a target system into operation.
-
Validation - detects deviations between the state known in DirX Identity and the state in the connected system, for example accounts or groups that were created or deleted outside of DirX Identity, and writes a message about each deviation into the "to do" field (
dxrToDo) of the affected target system object.
Both modes update the dxrTSState attribute and the group member attributes of the affected target
system objects.
LDAP2Ident_Validation validates a connected LDAP directory against the corresponding target system subtree in the Identity Store. Both activities run with MetaCP, first for accounts and then for groups.
Use this workflow when you want scheduled validation of LDAP data without a separate connector-specific export agent.
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 |
Target Scheduled / LDAP |
Technology |
Tcl-based scheduled workflow |
LDAP object class |
|
Workflow type |
|
Connected system / controller type |
- |
Configuration wizard |
|
Active in the factory data |
not set |
Factory data version |
7.0 |
Factory data path |
|
Prerequisites
-
Configure
MetaCPfor the LDAP connected directory. -
Create and configure the LDAP connected directory and the corresponding target system subtree in the Identity Store.
Workflow and Activities
| Step | Activity | Description | Agent | Runs after |
|---|---|---|---|---|
1 |
|
import of accounts |
|
start activity |
2 |
|
Import of groups |
|
|
Jobs and Agents
| Activity | Job | Agent | Operation | Input channel | Output channel |
|---|---|---|---|---|---|
|
|
|
Delta Import |
|
|
|
|
|
Delta Import |
|
|
Configuration Parameters
| Parameter | Default value |
|---|---|
|
InitialLoad |
| Parameter | Default value |
|---|---|
|
0 |
|
full |
|
0 |
|
FALSE |
|
REAL |
|
10 |
|
0 |
|
TRUE |
|
FALSE |
|
1 |
|
0 |
| Parameter | Default value |
|---|---|
|
0 |
|
full |
|
0 |
|
FALSE |
|
REAL |
|
10 |
|
0 |
|
TRUE |
|
FALSE |
|
1 |
|
0 |
A Tcl-based workflow runs scheduled in the C++-based Server (IdS-C). Its activities run in the order
defined by the dxmPredecessorActivity-DN chain, and each activity starts a job that runs one agent
with one input and one output channel. Agents exchange their data through files or directly through
the meta controller, so a typical workflow consists of an export activity that writes the data of the
connected system and an import activity that maps and loads that data into the Identity Store.
You start these workflows manually from the Identity Manager or attach them to a schedule.
In this workflow, the C++-based Server runs these activities in sequence:
-
LDAP2Ident_ValAccount_MetaCPvalidates and imports LDAP account data into the Identity Store validation flow. -
LDAP2Ident_ValGroup_MetaCPvalidates and imports LDAP group data into the Identity Store validation flow.
If one activity fails, the workflow stops at that point and the remaining activities do not run.
Operation
-
Start
LDAP2Ident_Validationmanually or on a schedule. -
The workflow first processes accounts through
LDAP2Ident_ValAccount_MetaCPand then processes groups throughLDAP2Ident_ValGroup_MetaCP. -
Because both steps run with
MetaCP, the workflow performs the whole validation pass through the LDAP connector configuration of the target system. -
Depending on the selected
mode, the run either refreshes the target system subtree from LDAP or records deviations between LDAP and the Identity Store on the affected target system objects. -
When the workflow completes successfully, the LDAP validation pass has covered both accounts and groups.