Validate_JDBC_Realtime

Sample workflow to validate an JDBC database against a 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_JDBC_Realtime is the validation workflow for connected systems of type JDBC. You use it to compare the managed database objects in the JDBC connected directory with the corresponding target system data in the Identity Store.

The sample validates the same object areas that DirX Identity manages through accounts, groups, and members. The TS port also exposes setPassword, and the workflow applies CryptFilter and JDBCFilter before it hands a request to 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

Validate_JDBC_Realtime

Category

Target Realtime / JDBC

Technology

Java-based real-time workflow

LDAP object class

dxmIDMWorkflowDefinition

Workflow type

ProvisionTS

Connected system / controller type

JDBC

Configuration wizard

wf-Provisioning-Validate.xml

Active in the factory data

FALSE

Factory data version

8.0

Factory data path

Workflows/Default/Target Realtime/JDBC/Validate_JDBC_Realtime

Prerequisites

  • You need a connected directory of type JDBC with bind profile JDBC Database Admin.

  • You need a target system of type JDBC in the Identity Store that represents the same database objects over accounts, groups, and members.

  • The Java-based Server (IdS-J) must reach the Identity Store through Domain_Admin and the JDBC 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

JDBCConnector

JDBC

JDBC Database Admin

not set

Channels

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

accounts

Channel for accounts

OneToOne

SearchAttributes

groups

Channel for groups

OneToOne

SearchAttributes

members

Channel for account - group memberships

OneToOne

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

accounts

Channel for accounts

OneToOne

SearchAttributes

groups

Channel for groups

OneToOne

SearchAttributes

members

Channel for account - group memberships

OneToOne

SearchAttributes

setPassword

Channel for setting a password

OneToOne

SearchAttributes

Filters

Port Filter Description Sequence

TS

CryptFilter

decryption

1

TS

JDBCFilter

jdbc filter

2

Configuration Parameters

Table 3. Workflow parameters of Validate_JDBC_Realtime
Parameter Default value

timeout

P0Y0M4DT0H0M0S
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

JDBC

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

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

decrypt.attribute

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

decrypt.attribute

password

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 compares the entries that DirX Identity selects on IdentityDomain with the corresponding entries that the TS port reads through JDBCConnector. It works on accounts, groups, and members, and the TS port also exposes setPassword for requests that include password data.

Before the connector sees a request, CryptFilter decrypts protected values and JDBCFilter applies the JDBC-specific request handling. The event port can publish JMS messages and the notify port can send workflow notifications. 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. DirX Identity creates a validation request for the target system subtree of JDBC.

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

  3. The IdentityDomain port reads the relevant objects from the Identity Store over accounts, groups, and members.

  4. The TS port reads the matching data in the JDBC connected directory; CryptFilter decrypts protected values and JDBCFilter prepares the JDBC-specific access.

  5. The workflow evaluates whether both sides match and returns the result to DirX Identity.

  6. The event and notify ports handle the configured follow-up notifications for the processed request.

  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.