CreatePersonasForNonPrimaryAccounts
Perform Execution of the Consistency Rule CreatePersonasForNonPrimaryAccounts in Identity Store
CreatePersonasForNonPrimaryAccounts executes the consistency rule of the same name over all
accounts in the Identity Store that are not designated as primary accounts and have no associated
persona. For each qualifying account the PolicyAgent creates a persona entry and links it to
the owning user, giving the secondary account a proper identity representation in the Identity
Store.
Run this workflow during initial configuration or periodically as a remediation step when non-primary accounts without personas are found in the system.
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 |
Identity Store |
Technology |
Tcl-based scheduled workflow |
LDAP object class |
|
Workflow type |
- |
Connected system / controller type |
- |
Configuration wizard |
|
Active in the factory data |
not set |
Factory data version |
7.0 |
Factory data path |
|
Prerequisites
-
The
CreatePersonasForNonPrimaryAccountsconsistency rule must be configured in the Identity Store. -
The
PersonasForNonPrimaryAccounts inandPersonasForNonPrimaryAccounts outchannels must be configured in the C++-based Server.
Workflow and Activities
| Step | Activity | Description | Agent | Runs after |
|---|---|---|---|---|
1 |
|
Policy execution via DirX Identity Policy agent |
|
start activity |
Jobs and Agents
| Activity | Job | Agent | Operation | Input channel | Output channel |
|---|---|---|---|---|---|
|
|
|
Full Import |
|
|
Configuration Parameters
| Parameter | Default value |
|---|---|
|
full |
|
0 |
|
AssignOnly |
|
process |
|
2 |
A Tcl-based workflow runs scheduled in the C++-based Server (IdS-C). Its activities run in the order
defined by the dxmPredecessorActivity-DN chain, and each activity starts a job that runs one agent
with one input and one output channel. Agents exchange their data through files or directly through
the meta controller, so a typical workflow consists of an export activity that writes the data of the
connected system and an import activity that maps and loads that data into the Identity Store.
You start these workflows manually from the Identity Manager or attach them to a schedule.
The workflow has a single activity, PersonasForNonPrimaryAccounts, which runs the PolicyAgent
job of the same name. The job reads non-primary accounts without a persona from the
PersonasForNonPrimaryAccounts in input channel and writes the created persona entries to the
PersonasForNonPrimaryAccounts out output channel. The mode is AssignOnly and the request
is process.
Operation
-
You start the workflow manually from the Identity Manager or attach it to a schedule.
-
The C++-based Server starts the
PersonasForNonPrimaryAccountsactivity and launches thePolicyAgentjob. -
The agent reads accounts from the Identity Store through the
PersonasForNonPrimaryAccounts ininput channel; the channel filter selects non-primary accounts that have no associated persona. -
For each matching account the consistency rule creates a persona entry and links it to the owning user.
-
The results are written through the
PersonasForNonPrimaryAccounts outoutput channel.