Validate_Medico_Realtime

Sample workflow to provision a Medico connected system from DirX Identity target system.

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.

Validate_Medico_Realtime is the validation workflow for connected systems of type Medico. It checks that the Medico Login, Person, Group, Profile, and Role objects represented in the Identity Store still match the connected system, and it re-applies changes when validation creates a provisioning request. The sample parameters identify the target system as tsresource medico in cluster medico.

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

Validate_Medico_Realtime

Category

Target Realtime / Medico

Technology

Java-based real-time workflow

LDAP object class

dxmIDMWorkflowDefinition

Workflow type

ProvisionTS

Connected system / controller type

Medico

Configuration wizard

wf-Provisioning-MedicoValidate.xml

Active in the factory data

FALSE

Factory data version

8.0

Factory data path

Workflows/Default/Target Realtime/Medico/Validate_Medico_Realtime

Prerequisites

  • A connected directory of type Medico that uses Spmlv1SoapConnector2TS, with the bind profile Dummy set so the workflow can read and update the Medico system.

  • A target system of type Medico in the Identity Store that is linked to that connected directory and already represents the Medico objects that you want to validate.

  • The Java-based Server that runs the workflow must be able to reach both the Identity Store and the Medico endpoint; SSL is not enabled on the TS port in the factory data.

Workflow and Activities

Activity Type Component description Description Ports

error

error

provisioningActivity

Error Activity

Message

join

ProvisionTS

provisioningActivity

Join activity for the provision-to-TS workflow

event, IdentityDomain, notify, ts

Ports

Activity Port Component description Connector Connected directory Bind profile SSL

error

Message

errorPort

ErrorNotifyMailConnector

-

-

not set

join

event

notificationPort

JmsConnector

-

-

not set

join

IdentityDomain

provisioningPort

LdapConnector

Identity Store

Domain_Admin

not set

join

notify

notificationPort

NotifyMailConnector

-

-

not set

join

TS

provisioningPort

Spmlv1SoapConnector2TS

Medico

Dummy

not set

Channels

Table 1. Channels of port IdentityDomain (activity join)
Channel Description Reference type Delta type

group

Channel for groups

not set

SearchAttributes

login

Channel for accounts

not set

SearchAttributes

person

Channel for accounts

ManyToOne

SearchAttributes

profile

Channel for profiles

not set

SearchAttributes

role

Channel for roles

not set

SearchAttributes
Table 2. Channels of port TS (activity join)
Channel Description Reference type Delta type

groups

Channel for medico groups

not set

not set

logins

Channel for accounts of type login

not set

not set

persons

Channel for accounts of type person

ManyToOne

not set

profiles

Channel for accounts of type person

not set

not set

roles

Channel for accounts of type person

not set

not set

setPassword

Channel for setting a password

ManyToOne

not set

Filters

Port Filter Description Sequence

TS

MedicoCryptFilter

encrypt pawo

1

Configuration Parameters

Table 3. Workflow parameters of Validate_Medico_Realtime
Parameter Default value

timeout

P0Y0M4DT0H0M0S

tscluster

medico

tsresource

medico
Table 4. Parameters of activity error
Parameter Default value

resourcefamily

Mail

retrylimit

3

timeout

P0Y0M1DT0H0M0S

waitbeforeretry

P0Y0M0DT2H0M0S
Table 5. Parameters of port Message (activity error)
Parameter Default value

decrypt.attribute

dxmPassword
Table 6. Parameters of activity join
Parameter Default value

resourcefamily

Medico

retrylimit

3

timeout

P0Y0M1DT0H0M0S

waitbeforeretry

P0Y0M0DT0H30M0S
Table 7. Parameters of port event (activity join)
Parameter Default value

appid

event

decrypt.attribute

userPassword

tgtisjmsclient

false
Table 8. Parameters of port IdentityDomain (activity join)
Parameter Default value

decrypt.attribute

userPassword
Table 9. Parameters of port notify (activity join)
Parameter Default value

decrypt.attribute

userPassword
Table 10. Parameters of port TS (activity join)
Parameter Default value

decrypt.attribute

userPassword

ssltoidsc

FALSE

A Java-based real-time workflow runs as a permanently loaded configuration in the Java-based Server (IdS-J). It is triggered by a request or an event rather than by a schedule. Each workflow consists of activities; an activity opens one port per system it talks to, and each port uses a connector to reach that system.

Most provisioning workflows contain a join activity that performs the actual work and an error activity that receives requests which still fail after all retries and sends a notification about them. The retrylimit, waitbeforeretry and timeout parameters of an activity control how often and how long a failed request is retried before it is handed to the error activity.

The event port publishes change events over JMS, and the notify port sends e-mail notifications. Neither port is bound to a connected directory.

The join activity handles the validation request. Its IdentityDomain port reads the affected Medico objects from the group, login, person, profile, and role channels in the Identity Store, and its TS port writes the corresponding state to Medico on the groups, logins, persons, profiles, roles, and setPassword channels. MedicoCryptFilter prepares protected values before they are sent to Medico.

A request that fails is retried up to 3 times (retrylimit) with 30 minutes between the attempts (waitbeforeretry). If it still fails, the error activity takes it over and sends a notification through the Message port; the workflow parameter timeout gives a request 4 days before it is discarded.

Operation

  1. Validation marks the affected Medico object in the target system subtree of the Identity Store.

  2. The Java-based Server passes the resulting request to the join activity of this workflow.

  3. The IdentityDomain port reads the affected entry from the Identity Store over the matching channel.

  4. The TS port checks the Medico object and applies the required correction on the corresponding Medico channel.

  5. The result is written back into the Identity Store so that the request state reflects what happened in Medico.

  6. The event port publishes the change as a JMS event for applications that listen to provisioning events; the notify port sends the configured e-mail notifications.

  7. Requests that fail permanently are handed to the error activity, which reports them by e-mail.

The workflow is delivered inactive (dxmActive is FALSE). Copy it into your own scenario, connect the copy to your connected directory and activate the copy.