RACF2Ident_Validation

Workflow for Validation from RACF to 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.

RACF2Ident_Validation validates an IBM RACF connected system against the corresponding target system subtree in the Identity Store. Both validation steps run with MetaCP and cover accounts first, then groups.

Use this workflow when you want scheduled validation of RACF data through the configured MetaCP mapping.

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

RACF2Ident_Validation

Category

Target Scheduled / RACF

Technology

Tcl-based scheduled workflow

LDAP object class

dxmWorkflow

Workflow type

Validation

Connected system / controller type

-

Configuration wizard

LDAP-LDAP

Active in the factory data

not set

Factory data version

7.0

Factory data path

Workflows/Default/Target Scheduled/RACF/RACF2Ident_Validation

Prerequisites

  • Configure MetaCP for the connected IBM RACF system.

  • Create and configure the RACF connected system and the corresponding target system subtree in the Identity Store.

Workflow and Activities

Step Activity Description Agent Runs after

1

RACF2Ident_ValAccount_MetaCP

Import of accounts

MetaCP

start activity

2

RACF2Ident_ValGroup_MetaCP

Import of groups

MetaCP

RACF2Ident_ValAccount_MetaCP

Jobs and Agents

Activity Job Agent Operation Input channel Output channel

RACF2Ident_ValAccount_MetaCP

RACF2Ident_ValAccount_MetaCP

MetaCP

Delta Import

RACF2Ident_ValAccount

RACF2Ident_ValAccount

RACF2Ident_ValGroup_MetaCP

RACF2Ident_ValGroup_MetaCP

MetaCP

Delta Import

RACF2Ident_ValGroup

RACF2Ident_ValGroup

Configuration Parameters

Table 1. Workflow parameters of RACF2Ident_Validation
Parameter Default value

mode

InitialLoad
Table 2. Parameters of job RACF2Ident_ValAccount_MetaCP
Parameter Default value

debug_trace

0

delta_mode

full

delta_on

0

exact_action

FALSE

init_mode

REAL

max_trace_entries

10

notify_not_ok

0

statistics

TRUE

test_mapping_only

FALSE

trace_level

1

trace_recordcount

0
Table 3. Parameters of job RACF2Ident_ValGroup_MetaCP
Parameter Default value

debug_trace

0

delta_mode

full

delta_on

0

exact_action

FALSE

init_mode

REAL

max_trace_entries

10

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. RACF2Ident_ValAccount_MetaCP validates and imports account data from the RACF system.

  2. RACF2Ident_ValGroup_MetaCP validates and imports group data from the RACF system.

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

Operation

  1. Start RACF2Ident_Validation manually or on a schedule.

  2. The workflow first processes account data through RACF2Ident_ValAccount_MetaCP and then processes group data through RACF2Ident_ValGroup_MetaCP.

  3. Because both steps run with MetaCP, the workflow performs the whole validation pass through the configured RACF connector mapping.

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

  5. When the workflow completes successfully, the validation pass has covered both accounts and groups.