JDBC2Ident_Validation

Workflow for Validation between JDBC 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.

JDBC2Ident_Validation validates the content of a JDBC-connected database against the corresponding target system subtree in the Identity Store. It exports groups and accounts with JDBCExport and imports them with MetaCP so that DirX Identity can compare both sides.

The workflow processes groups first and accounts second during the validation run.

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

JDBC2Ident_Validation

Category

Target Scheduled / JDBC

Technology

Tcl-based scheduled workflow

LDAP object class

dxmWorkflow

Workflow type

Validation

Connected system / controller type

-

Configuration wizard

JDBC-LDAP

Active in the factory data

not set

Factory data version

7.0

Factory data path

Workflows/Default/Target Scheduled/JDBC/JDBC2Ident_Validation

Prerequisites

  • Configure JDBCExport for the JDBC-connected database that you want to validate.

  • Configure MetaCP for the corresponding target system subtree in the Identity Store.

Workflow and Activities

Step Activity Description Agent Runs after

1

JDBC2Ident_JDBCExport

Export groups/memberships from JDBC

JDBCAgent

start activity

2

JDBC2Ident_ValGroup_MetaCP

import groups/memberships to Role

MetaCP

JDBC2Ident_JDBCExport

3

JDBC2Ident_ValAccount_JDBCExport

export accounts from JDBC

JDBCAgent

JDBC2Ident_ValGroup_MetaCP

4

JDBC2Ident_ValAccount_MetaCP

import accounts to Role

MetaCP

JDBC2Ident_ValAccount_JDBCExport

Jobs and Agents

Activity Job Agent Operation Input channel Output channel

JDBC2Ident_JDBCExport

JDBC2Ident_ValGroup_JDBCExport

JDBCAgent

Full Export

JDBC2Ident_ValGroup

OutData

JDBC2Ident_ValGroup_MetaCP

JDBC2Ident_ValGroup_MetaCP

MetaCP

Delta Import

InData

JDBC2Ident_ValGroup1

JDBC2Ident_ValAccount_JDBCExport

JDBC2Ident_ValAccount_JDBCExport

JDBCAgent

Full Export

JDBC2Ident_ValAccount

OutData

JDBC2Ident_ValAccount_MetaCP

JDBC2Ident_ValAccount_MetaCP

MetaCP

Full Export

InData

JDBC2Ident_ValAccount1

Configuration Parameters

Table 1. Workflow parameters of JDBC2Ident_Validation
Parameter Default value

mode

InitialLoad
Table 2. Parameters of job JDBC2Ident_ValGroup_JDBCExport
Parameter Default value

controller_tracelevel

9

delta_mode

full

delta_on

0
Table 3. Parameters of job JDBC2Ident_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

test_max_entries

10

trace_level

1

trace_recordcount

0
Table 4. Parameters of job JDBC2Ident_ValAccount_JDBCExport
Parameter Default value

controller_tracelevel

9

delta_mode

full

delta_on

0
Table 5. Parameters of job JDBC2Ident_ValAccount_MetaCP
Parameter Default value

debug_trace

13

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

test_max_entries

10

trace_level

2

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. JDBC2Ident_JDBCExport exports group data from the JDBC-connected database.

  2. JDBC2Ident_ValGroup_MetaCP imports that group data into the Identity Store validation flow.

  3. JDBC2Ident_ValAccount_JDBCExport exports account data from the JDBC-connected database.

  4. JDBC2Ident_ValAccount_MetaCP imports that account 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

  1. Start JDBC2Ident_Validation manually or on a schedule.

  2. The workflow first exports group data with JDBC2Ident_JDBCExport and imports it with JDBC2Ident_ValGroup_MetaCP.

  3. It then exports account data with JDBC2Ident_ValAccount_JDBCExport and imports it with JDBC2Ident_ValAccount_MetaCP.

  4. Depending on the selected mode, the run either refreshes the target system subtree from the JDBC data or records deviations between the JDBC-connected database and the Identity Store on the affected target system objects.

  5. When the workflow completes successfully, DirX Identity has processed both group and account data for the JDBC target system.