Ident_Medico_Realtime

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

A provisioning workflow transfers the account, group and membership changes that DirX Identity has calculated for a target system into the connected system, and acknowledges the result back into the Identity Store. It is the workflow that executes what privilege resolution has decided: when a user gains or loses a privilege, the resolution writes the resulting account or membership change into the target system subtree of the Identity Store, and this workflow applies that change to the connected system.

The workflow processes single requests as they arrive, so it reflects changes with little delay. Use the corresponding validation workflow to detect changes that were made in the connected system outside of DirX Identity.

Ident_Medico_Realtime is the provisioning workflow for connected systems of type Medico. You use it to keep the Medico target system aligned with the corresponding target system subtree in the Identity Store.

The workflow maps several Medico-specific object areas. On IdentityDomain, it reads group, login, person, profile, and role; on TS, it writes them as groups, logins, persons, profiles, and roles. Password changes go through setPassword, and MedicoCryptFilter prepares protected values for the connector.

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_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-MedicoSynchronize.xml

Active in the factory data

FALSE

Factory data version

8.0

Factory data path

Workflows/Default/Target Realtime/Medico/Ident_Medico_Realtime

Prerequisites

  • You need a connected directory of type Medico with bind profile Dummy.

  • You need a target system of type Medico in the Identity Store, in the sample context tscluster medico and tsresource medico.

  • The Java-based Server (IdS-J) must reach the Identity Store through Domain_Admin and the Medico connected directory through the TS port.

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 Ident_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 maps the Medico-specific channels from IdentityDomain to the TS port. person and persons, as well as setPassword, use ManyToOne; the other channels handle group, login, profile, and role data.

The TS port uses Spmlv1SoapConnector2TS. MedicoCryptFilter runs before the connector, and the port parameter ssltoidsc is FALSE in the sample. If processing still fails after three retries with a 30-minute wait, the workflow routes the request to error, which sends the error notification through Message.

Operation

  1. Privilege resolution writes a change into the Medico target system subtree of the Identity Store.

  2. The Java-based Server (IdS-J) passes the resulting request to join.

  3. The IdentityDomain port reads the affected group, login, person, profile, or role entry from the Identity Store.

  4. The TS port writes the corresponding groups, logins, persons, profiles, or roles entry to the Medico connected directory and uses setPassword when the request contains password data.

  5. DirX Identity records the provisioning result back in the target system entry state.

  6. The event port publishes the change as a JMS event and the notify port sends the configured e-mail notifications.

  7. Requests that fail permanently are handed to error, 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.