Ident_Imprivata_Realtime
Sample workflow to provision a Imprivata OneSign 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_Imprivata_Realtime is the provisioning workflow for connected systems of type Imprivata OneSign. You use it to keep an Imprivata OneSign target system aligned with the target system objects that DirX Identity groups under tsresource imprivata-domain and tscluster imprivata-cluster.
On the target side, the accounts channel represents subscribers. Together with groups and the available setPassword channel, the workflow covers the core objects that Spmlv1SoapConnector2Imprivata exposes for real-time provisioning.
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 Realtime / Imprivata OneSign |
Technology |
Java-based real-time workflow |
LDAP object class |
|
Workflow type |
|
Connected system / controller type |
|
Configuration wizard |
|
Active in the factory data |
FALSE |
Factory data version |
8.0 |
Factory data path |
|
Prerequisites
-
Create a connected directory of type
Imprivata OneSignwith the bind profileAdmin. -
Link that connected directory to a target system of type
Imprivata OneSignin the Identity Store. -
Make sure the Java-based Server can reach the Identity Store through
Domain_Admin, the connected directory throughSpmlv1SoapConnector2Imprivata, and the messaging system used byevent.
Workflow and Activities
| Activity | Type | Component description | Description | Ports |
|---|---|---|---|---|
|
|
|
Error Activity |
|
|
|
|
Join activity for the provision-to-TS workflow |
|
Ports
| Activity | Port | Component description | Connector | Connected directory | Bind profile | SSL |
|---|---|---|---|---|---|---|
|
|
|
|
- |
- |
not set |
|
|
|
|
- |
- |
not set |
|
|
|
|
|
|
not set |
|
|
|
|
- |
- |
not set |
|
|
|
|
|
|
not set |
Channels
| Channel | Description | Reference type | Delta type |
|---|---|---|---|
|
Channel for accounts |
OneToOne |
SearchAttributes |
|
Channel for groups |
OneToOne |
SearchAttributes |
| Channel | Description | Reference type | Delta type |
|---|---|---|---|
|
Channel for subscribers |
OneToOne |
SearchAttributes |
|
Channel for groups |
OneToOne |
SearchAttributes |
|
Channel for setting a password |
OneToOne |
SearchAttributes |
Configuration Parameters
| Parameter | Default value |
|---|---|
|
P0Y0M4DT0H0M0S |
|
imprivata-cluster |
|
imprivata-domain |
| Parameter | Default value |
|---|---|
|
SPMLv1 |
|
3 |
|
P0Y0M1DT0H0M0S |
|
P0Y0M0DT2H0M0S |
| Parameter | Default value |
|---|---|
|
dxmPassword |
| Parameter | Default value |
|---|---|
|
SPMLv1 |
|
3 |
|
P0Y0M1DT0H0M0S |
|
P0Y0M0DT0H30M0S |
| Parameter | Default value |
|---|---|
|
event |
|
userPassword |
|
false |
| Parameter | Default value |
|---|---|
|
userPassword |
| Parameter | Default value |
|---|---|
|
userPassword |
| Parameter | Default value |
|---|---|
|
password |
|
My-Company |
|
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 receives provisioning work on event, reads the DirX Identity side on IdentityDomain, and sends the resulting work to TS. On the Imprivata side, accounts means subscribers, while groups stays available for the related group assignments.
notify handles the normal notification path. If provisioning fails, the workflow switches to error and sends the failure message through Message.
Operation
-
A provisioning event reaches
jointhroughevent. -
joinreads the required subscriber and group context fromIdentityDomain. -
CryptFilterdecrypts the target-side password value onTS, andSpmlv1SoapConnector2Imprivatasends the target request to the connected directory. -
The workflow sends the normal notification through
notify. -
If the target request fails, the workflow routes the error to
errorand sends the failure information throughMessage.
The workflow is delivered inactive (dxmActive is FALSE). Copy it into your own scenario before you enable it.