SetPassword in SAPR3UM
Sets the password in an SAPR3UM connected system
A set-password workflow propagates a password from DirX Identity to the accounts of one connected
system. It is triggered when a user or an administrator changes a password in the Identity Store, or
when the password synchronization workflows distribute a password change. The workflow reads the
password over the setPassword channel of the Identity Store port and writes it through the target
system port; it does not synchronize any other account attribute.
Because a set-password workflow carries credentials, its ports decrypt the password attribute
explicitly through the decrypt.attribute parameter, and failures are reported by a dedicated
password notification connector instead of the regular notification connector.
SetPassword in SAPR3UM sends password changes from DirX Identity to connected systems of type
SAPR3UM. You use it when the Identity Store is authoritative for account passwords in the SAP user
management environment addressed by tscluster and tsresource.
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 / SAP R3 UM |
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.1 |
Factory data path |
|
Prerequisites
-
A connected directory of type
SAPR3UMthat points to the SAP user management system, with the bind profileSAPR3UMprofileset to credentials that may change user passwords. -
A target system of type
SAPR3UMin the Identity Store that is linked to that connected directory. -
The Java-based Server that runs the workflow must be able to reach both the SAP user management system 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 Activity |
|
|
|
|
setPassword activitity to update passwords in an SAPR3UM connected system |
|
Ports
| Activity | Port | Component description | Connector | Connected directory | Bind profile | SSL |
|---|---|---|---|---|---|---|
|
|
|
|
- |
- |
not set |
|
|
|
|
|
|
not set |
|
|
|
|
- |
- |
not set |
|
|
|
|
|
|
not set |
Channels
| Channel | Description | Reference type | Delta type |
|---|---|---|---|
|
Channel for accounts |
not set |
SearchAttributes |
|
Channel for groups |
not set |
SearchAttributes |
|
Channel for members |
not set |
not set |
| Channel | Description | Reference type | Delta type |
|---|---|---|---|
|
Channel for accounts |
not set |
SearchAttributes |
|
Channel for groups |
not set |
SearchAttributes |
|
Channel for members |
not set |
not set |
|
Channel for setting a password |
not set |
not set |
Configuration Parameters
| Parameter | Default value |
|---|---|
|
P0Y0M4DT0H0M0S |
|
dxm.setPasswordRequest. |
|
localhost |
|
SAP_R3_UM |
| Parameter | Default value |
|---|---|
|
|
|
3 |
|
P0Y0M1DT0H0M0S |
|
P0Y0M0DT2H0M0S |
| Parameter | Default value |
|---|---|
|
dxmPassword |
| Parameter | Default value |
|---|---|
|
SAPR3UM |
|
3 |
|
P0Y0M1DT0H0M0S |
|
P0Y0M0DT0H30M0S |
| Parameter | Default value |
|---|---|
|
userPassword |
| Parameter | Default value |
|---|---|
|
userPassword |
| Parameter | Default value |
|---|---|
|
PASSWORD.BAPIPWD |
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 SetPassword activity propagates the password change. Its IdentityDomain port resolves the
affected target system entry in the Identity Store over the accounts, groups and members
channels, and its TS port writes the new password into SAPR3UM over the setPassword channel.
The CryptFilter on the TS port decrypts the protected password value before the connector sends
it, and the notify port sends the configured password notification.
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
-
A password change in the Identity Store creates a provisioning request for the affected
SAPR3UMaccount. -
The Java-based Server passes the request to the
SetPasswordactivity of this workflow. -
The
IdentityDomainport reads the affected target system object from the Identity Store. -
The
TSport decrypts the protected password value and writes it to the connectedSAPR3UMsystem over thesetPasswordchannel. -
The result is written back into the Identity Store so that the request state reflects the outcome.
-
The
notifyport sends the configured password notification e-mails. -
Requests that fail permanently are handed to the
erroractivity, 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.