Validate_SharePoint_Ident_Clustered

Sample workflow to validate a cluster of SharePoint sites against the corresponding DirX Identity target systems

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_SharePoint_Ident_Clustered validates SharePoint groups and memberships in a cluster against the corresponding target system objects in the Identity Store. You use it to detect differences between the sites and the DirX Identity model without restricting the workflow to one fixed site.

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_SharePoint_Ident_Clustered

Category

Target Realtime / SharePoint

Technology

Java-based real-time workflow

LDAP object class

dxmIDMWorkflowDefinition

Workflow type

ProvisionTS

Connected system / controller type

-

Configuration wizard

LDAP-SharePoint

Active in the factory data

FALSE

Factory data version

8.0

Factory data path

Workflows/Default/Target Realtime/SharePoint/Validate_SharePoint_Ident_Clustered

Prerequisites

  • A connected directory of type SharePoint that points to the SharePoint environment, with the bind profile BA_Admin set to credentials that may read the groups and memberships that you want to validate.

  • Target systems of type SharePoint in the Identity Store that are linked to that connected directory.

  • The Java-based Server that runs the workflow must be able to reach both the SharePoint environment and the Identity Store; the Identity Store is accessed through the bind profile Domain_Admin.

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

SharePointConnector

SharePoint

BA_Admin

not set

Channels

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

groups

Channel for groups

not set

SearchAttributes

members

Channel for members

not set

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

groups

Channel for groups

not set

not set

members

Channel for members

not set

not set

Filters

Port Filter Description Sequence

TS

CryptFilter

decryption

1

Configuration Parameters

Table 3. Workflow parameters of Validate_SharePoint_Ident_Clustered
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

LDAP

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

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 performs the validation work. Its IdentityDomain port reads the expected state from the Identity Store over the groups and members channels, and its TS port compares that state with the current content of the SharePoint sites. The workflow therefore validates site groups and their memberships only. The CryptFilter on the TS port decrypts protected attributes before the connector evaluates them.

A request that fails is retried up to three 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 four days before it is discarded.

Operation

  1. You start a validation run for the relevant SharePoint target systems in the cluster.

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

  3. The IdentityDomain port reads the expected groups and memberships from the Identity Store.

  4. The TS port reads the current groups and memberships from the corresponding SharePoint sites and compares them with the state stored in DirX Identity.

  5. Deviations are written back into the Identity Store, where DirX Identity updates the validation state and records follow-up work on the affected target system objects.

  6. The event port publishes the validation result as a JMS event; 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.