Ident_NDS_Sync

Workflow for Export from Identity Store and Import to NDS and backwards

Ident_NDS_Sync propagates account and group changes from the Identity Store to a connected NDS or eDirectory installation. Both activities run with MetaCP, which exports the data from the Identity Store and applies the mapped changes to the NDS side.

Use this workflow when DirX Identity is the scheduled source for the NDS target system and no return synchronization step is part of the workflow.

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

Ident_NDS_Sync

Category

Target Scheduled / NDS

Technology

Tcl-based scheduled workflow

LDAP object class

dxmWorkflow

Workflow type

Sync

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/NDS/Ident_NDS_Sync

Prerequisites

  • Configure MetaCP with the NDS or eDirectory connector for the connected directory.

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

Workflow and Activities

Step Activity Description Agent Runs after

1

Ident_NDS_SyncAccount_MetaCP

Synchronization of accounts

MetaCP

start activity

2

Ident_NDS_SyncGroup_MetaCP

Synchronization of groups

MetaCP

Ident_NDS_SyncAccount_MetaCP

Jobs and Agents

Activity Job Agent Operation Input channel Output channel

Ident_NDS_SyncAccount_MetaCP

Ident_NDS_SyncAccount_MetaCP

MetaCP

Full Export

Ident2NDS_SyncAccount

Ident2LDAP_SyncAccount

Ident_NDS_SyncGroup_MetaCP

Ident_NDS_SyncGroup_MetaCP

MetaCP

Full Export

Ident2NDS_SyncGroup

Ident2LDAP_SyncGroup

Configuration Parameters

Table 1. Parameters of job Ident_NDS_SyncAccount_MetaCP
Parameter Default value

debug_trace

0

delta_mode

delta-or-full

delta_on

1

exact_action

FALSE

init_mode

REAL

max_trace_entries

10

notify_not_ok

0

statistics

TRUE

test_mapping_only

FALSE

test_max_entries

0

trace_level

1

trace_recordcount

0
Table 2. Parameters of job Ident_NDS_SyncGroup_MetaCP
Parameter Default value

debug_trace

0

delta_mode

delta-or-full

delta_on

1

exact_action

FALSE

init_mode

REAL

max_trace_entries

10

notify_not_ok

0

statistics

TRUE

test_mapping_only

FALSE

test_max_entries

0

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. Ident_NDS_SyncAccount_MetaCP exports account changes from the Identity Store and applies them to NDS.

  2. Ident_NDS_SyncGroup_MetaCP exports group changes from the Identity Store and applies them to NDS.

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

Operation

  1. Start Ident_NDS_Sync manually or on a schedule.

  2. The workflow first processes accounts through Ident_NDS_SyncAccount_MetaCP.

  3. When the account pass succeeds, Ident_NDS_SyncGroup_MetaCP processes the group changes.

  4. Because both activities run with MetaCP, the workflow remains a one-way export from the Identity Store to the NDS target system.

  5. A successful run applies the current scheduled account and group changes from the Identity Store to the connected NDS or eDirectory installation.