Validate_ShareFile_Realtime
Sample workflow to validate a Citrix ShareFile connected system 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_ShareFile_Realtime validates a connected system of type Citrix ShareFile against the state that DirX Identity keeps in the Identity Store. You use it when you want to check whether accounts, groups and members in the connected directory still match the ShareFile target system subtree.
The workflow uses the same CitrixShareFileConnector path as ordinary provisioning, so validation and any resulting corrective update use the same channels and connector settings. The factory data keeps dxminitialload at FALSE, so the sample is prepared for validation of an existing target system subtree.
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 / Citrix ShareFile |
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.3 |
Factory data path |
|
Prerequisites
-
You configure a connected directory of type
Citrix ShareFilethat usesCitrixShareFileConnectorand the bind profileAdmin. -
You make the
Identity Storeavailable through the bind profileDomain_Adminand theCitrix ShareFileconnected directory available through theTSport of the Java-based Server. -
You keep the relevant target system subtree in the Identity Store, so the workflow can read the expected state over
accounts,groupsandmembers.
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 for members |
OneToOne |
SearchAttributes |
| Channel | Description | Reference type | Delta type |
|---|---|---|---|
|
Channel for accounts |
OneToOne |
SearchAttributes |
|
Channel for groups |
OneToOne |
SearchAttributes |
|
Channel for members |
OneToOne |
SearchAttributes |
Configuration Parameters
| Parameter | Default value |
|---|---|
|
FALSE |
|
P0Y0M4DT0H0M0S |
| Parameter | Default value |
|---|---|
|
|
|
3 |
|
P0Y0M1DT0H0M0S |
|
P0Y0M0DT2H0M0S |
| Parameter | Default value |
|---|---|
|
dxmPassword |
| Parameter | Default value |
|---|---|
|
Citrix_ShareFile |
|
3 |
|
P0Y0M1DT0H0M0S |
|
P0Y0M0DT0H30M0S |
| Parameter | Default value |
|---|---|
|
event |
|
userPassword |
|
false |
| Parameter | Default value |
|---|---|
|
userPassword |
| Parameter | Default value |
|---|---|
|
userPassword |
| Parameter | Default value |
|---|---|
|
userPassword,dxmPassword |
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 reads the expected state from IdentityDomain and validates it against the connected directory through TS. It uses the accounts, groups and members channels on both ports. The CryptFilter decrypts userPassword,dxmPassword before CitrixShareFileConnector receives the request.
If processing fails, join retries the request three times and waits 30 minutes between attempts. If the request still fails, the workflow passes it to error, which sends the error notification through Message. The workflow-level timeout keeps the request for up to four days.
Operation
-
You start a validation request for the affected object in the
Citrix ShareFiletarget system subtree of the Identity Store. -
You let the Java-based Server route the request to
join. -
You let
IdentityDomainread the expected state overaccounts,groupsormembers. -
You let
TSvalidate the target-side state and apply the corresponding change when the connected directory does not match. -
You let the workflow write the result back to the Identity Store, publish the event through
eventand send the configured notification throughnotify. -
If the request still fails after the configured retries, you let
errorreport the failure throughMessage.
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.