Ident_SiPass_Sync

Workflow for synchronization to SiPass

Ident_SiPass_Sync synchronizes accounts between the Identity Store and a Siemens SiPass access control system in both directions. It first exports account changes from the Identity Store to SiPass and then exports the resulting account state from SiPass back into the Identity Store.

Use this workflow for scheduled bidirectional synchronization when the SiPass system remains an active source as well as a target of account changes.

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_SiPass_Sync

Category

Target Scheduled / SiPass

Technology

Tcl-based scheduled workflow

LDAP object class

dxmWorkflow

Workflow type

Sync

Connected system / controller type

-

Configuration wizard

LDAP-LDAP,SiPass

Active in the factory data

not set

Factory data version

7.0

Factory data path

Workflows/Default/Target Scheduled/SiPass/Ident_SiPass_Sync

Prerequisites

  • Configure SiPassAgent so that it can connect to the Siemens SiPass system.

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

Workflow and Activities

Step Activity Description Agent Runs after

1

Ident2SiPass_SyncAccount_MetaCP

Export of accounts

MetaCP

start activity

2

Ident2SiPass_SyncAccount_SiPassAgent

Import of accounts

SiPassAgent

Ident2SiPass_SyncAccount_MetaCP

3

SiPass2Ident_SyncAccount_SiPassAgent

Export of accounts

SiPassAgent

Ident2SiPass_SyncAccount_SiPassAgent

4

SiPass2Ident_SyncAccount_MetaCP

Import of accounts

MetaCP

SiPass2Ident_SyncAccount_SiPassAgent

Jobs and Agents

Activity Job Agent Operation Input channel Output channel

Ident2SiPass_SyncAccount_MetaCP

Ident2SiPass_SyncAccount_MetaCP

MetaCP

Full Export

Ident2SiPass_SyncAccount

OutData

Ident2SiPass_SyncAccount_SiPassAgent

Ident2SiPass_SyncAccount_SiPassAgent

SiPassAgent

Full Export

InData

Ident2SiPass_SyncAccount

SiPass2Ident_SyncAccount_SiPassAgent

SiPass2Ident_SyncAccount_SiPassAgent

SiPassAgent

Full Export

SiPass2Ident_SyncAccount

OutData

SiPass2Ident_SyncAccount_MetaCP

SiPass2Ident_SyncAccount_MetaCP

MetaCP

Delta Import

InData

SiPass2Ident_SyncAccount

Configuration Parameters

Table 1. Parameters of job Ident2SiPass_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

min_source_entries

0

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 Ident2SiPass_SyncAccount_SiPassAgent
Parameter Default value

controller_tracelevel

1

exactadd

FALSE

exactmod

FALSE

importdate

m/d/y
Table 3. Parameters of job SiPass2Ident_SyncAccount_SiPassAgent
Parameter Default value

controller_tracelevel

1

delta_mode

full

delta_on

0

exportdate

m/d/y
Table 4. Parameters of job SiPass2Ident_SyncAccount_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. Ident2SiPass_SyncAccount_MetaCP exports account changes from the Identity Store.

  2. Ident2SiPass_SyncAccount_SiPassAgent imports those account changes into SiPass.

  3. SiPass2Ident_SyncAccount_SiPassAgent exports account changes from SiPass.

  4. SiPass2Ident_SyncAccount_MetaCP imports those account changes into the Identity Store.

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

Operation

  1. Start Ident_SiPass_Sync manually or on a schedule.

  2. The workflow begins with the Identity Store to SiPass direction by exporting account changes with MetaCP and importing them with SiPassAgent.

  3. After the outbound pass finishes, SiPass2Ident_SyncAccount_SiPassAgent exports the resulting account data from SiPass.

  4. SiPass2Ident_SyncAccount_MetaCP then imports that returned account data into the Identity Store.

  5. When the workflow completes successfully, the scheduled run has applied outbound account changes to SiPass and has refreshed the account data for the SiPass target system subtree in the Identity Store.