Ident_LDAP_Sync
Workflow for Export from Identity Store and Import to LDAP and backwards
Ident_LDAP_Sync propagates account and group changes from the Identity Store to a connected LDAP directory. Both activities run with MetaCP, which exports the data from the Identity Store and applies the mapped changes to the LDAP side without a separate return synchronization step.
Use this workflow when the LDAP directory is updated from DirX Identity but no scheduled sync-back pass 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 |
|
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
MetaCPwith the LDAP connector for the connected LDAP 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 |
|
Synchronization of accounts |
|
start activity |
2 |
|
Synchronization of groups |
|
|
Jobs and Agents
| Activity | Job | Agent | Operation | Input channel | Output channel |
|---|---|---|---|---|---|
|
|
|
Full Export |
|
|
|
|
|
Full Export |
|
|
Configuration Parameters
| Parameter | Default value |
|---|---|
|
0 |
|
delta-or-full |
|
1 |
|
FALSE |
|
REAL |
|
10 |
|
0 |
|
TRUE |
|
FALSE |
|
0 |
|
1 |
|
0 |
| Parameter | Default value |
|---|---|
|
0 |
|
delta-or-full |
|
1 |
|
FALSE |
|
REAL |
|
10 |
|
0 |
|
TRUE |
|
FALSE |
|
0 |
|
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:
-
Ident_LDAP_SyncAccount_MetaCPexports account changes from the Identity Store and applies them to the LDAP directory. -
Ident_LDAP_SyncGroup_MetaCPexports group changes from the Identity Store and applies them to the LDAP directory.
If one activity fails, the workflow stops at that point and the remaining activities do not run.
Operation
-
Start
Ident_LDAP_Syncmanually or on a schedule. -
The workflow first processes accounts through
Ident_LDAP_SyncAccount_MetaCP. -
When the account pass succeeds,
Ident_LDAP_SyncGroup_MetaCPprocesses the group changes. -
Because both activities run with
MetaCP, the workflow stays in the Identity Store to LDAP direction for the whole run. -
A successful run applies the current scheduled account and group changes from the Identity Store to the connected LDAP directory.