ADS2Ident_Validation

Workflow for Validation between ODBC and Identity Store

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.

ADS2Ident_Validation validates the content of an Active Directory domain against the corresponding target system subtree in the Identity Store. For both object types, ADSAgent exports the data from the connected directory and MetaCP imports it so that DirX Identity can compare both sides.

The workflow processes accounts first and groups second. Use it for scheduled validation of an ADS target system that is already represented in the Identity Store.

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

ADS2Ident_Validation

Category

Target Scheduled / ADS

Technology

Tcl-based scheduled workflow

LDAP object class

dxmWorkflow

Workflow type

Validation

Connected system / controller type

-

Configuration wizard

ADS-LDAP

Active in the factory data

not set

Factory data version

7.0

Factory data path

Workflows/Default/Target Scheduled/ADS/ADS2Ident_Validation

Prerequisites

  • Configure ADSAgent for the connected directory of type ADS that points to the Active Directory domain you want to validate.

  • Configure MetaCP for the corresponding target system so that the imported account and group data is mapped to the target system subtree in the Identity Store.

Workflow and Activities

Step Activity Description Agent Runs after

1

ADS2Ident_ValAccount_ADSAgent

Full-Export from ADS for account validation

ADSAgent

start activity

2

ADS2Ident_ValAccount_MetaCP

import of accounts

MetaCP

ADS2Ident_ValAccount_ADSAgent

3

ADS2Ident_ValGroup_ADSAgent

Full-Export from ADS for group validation

ADSAgent

ADS2Ident_ValAccount_MetaCP

4

ADS2Ident_ValGroup_MetaCP

Import of groups

MetaCP

ADS2Ident_ValGroup_ADSAgent

Jobs and Agents

Activity Job Agent Operation Input channel Output channel

ADS2Ident_ValAccount_ADSAgent

ADS2Ident_ValAccount_ADSAgent

ADSAgent

Delta Export

ADS2Ident_ValAccount

OutData

ADS2Ident_ValAccount_MetaCP

ADS2Ident_ValAccount_MetaCP

MetaCP

Delta Import

InData

ADS2Ident_ValAccount

ADS2Ident_ValGroup_ADSAgent

ADS2Ident_ValGroup_ADSAgent

ADSAgent

Delta Export

ADS2Ident_ValGroup

OutData

ADS2Ident_ValGroup_MetaCP

ADS2Ident_ValGroup_MetaCP

MetaCP

Delta Import

InData

ADS2Ident_ValGroup

Configuration Parameters

Table 1. Workflow parameters of ADS2Ident_Validation
Parameter Default value

mode

InitialLoad
Table 2. Parameters of job ADS2Ident_ValAccount_ADSAgent
Parameter Default value

delta_mode

full

delta_on

0

trace

1
Table 3. Parameters of job ADS2Ident_ValAccount_MetaCP
Parameter Default value

debug_trace

0

delta_mode

full

delta_on

0

exact_action

FALSE

init_mode

REAL

max_trace_entries

10

min_source_entries

0

notify_not_ok

0

statistics

TRUE

test_mapping_only

FALSE

trace_level

1

trace_recordcount

0
Table 4. Parameters of job ADS2Ident_ValGroup_ADSAgent
Parameter Default value

delta_mode

full

delta_on

0

trace

1
Table 5. Parameters of job ADS2Ident_ValGroup_MetaCP
Parameter Default value

debug_trace

0

delta_mode

full

delta_on

0

exact_action

FALSE

init_mode

REAL

max_trace_entries

10

min_source_entries

0

notify_not_ok

0

statistics

TRUE

test_mapping_only

FALSE

trace_level

1

trace_recordcount

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:

  1. ADS2Ident_ValAccount_ADSAgent exports accounts from the Active Directory connected directory.

  2. ADS2Ident_ValAccount_MetaCP imports those account records into the Identity Store validation flow.

  3. ADS2Ident_ValGroup_ADSAgent exports groups from the same Active Directory connected directory.

  4. ADS2Ident_ValGroup_MetaCP imports those group records into the Identity Store validation flow.

If one activity fails, the workflow stops at that point and the remaining activities do not run.

Operation

  1. Start ADS2Ident_Validation manually from the Identity Manager or attach it to a schedule in the C++-based Server.

  2. The workflow exports account data from Active Directory with ADS2Ident_ValAccount_ADSAgent and imports it with ADS2Ident_ValAccount_MetaCP.

  3. After the account pass finishes, the workflow exports group data with ADS2Ident_ValGroup_ADSAgent and imports it with ADS2Ident_ValGroup_MetaCP.

  4. Depending on the selected mode, the validation run either loads the exported data into the target system subtree or records deviations between Active Directory and the Identity Store on the affected target system objects.

  5. When the workflow finishes successfully, DirX Identity has processed both account and group data for the connected ADS target system.