This rule places objects from one container in the Identity Vault into multiple containers in the data store on the OU attribute. Implement the rule on the Placement policy in the driver. You can implement the rule only on the Subscriber channel.
There are two steps involved in using the predefined rules: creating a policy in the Placement policy set, and importing the predefined rule. If you already have a Placement policy that you want to add this rule to, skip to Importing the Predefined Rule.
Open the
for the driver you want to manage.Click the Placement Policy object on the Subscriber channel.
Click
.Name the policy, make sure to implement the policy with the Policy Builder, then click
.The Rule Builder is launched.
Continue with Section 6.19.2, Importing the Predefined Rule.
In the Rule Builder, click
.Select
.To edit the rule, click
in the Rule Builder.Delete
from the field.Click the
icon to launch the Argument Builder.Select
in the Noun list, then click .In the Editor, add the parent container in the data store. The parent container must be specified in LDAP format. Make sure all of the department containers are child containers of this DN, then click
.Click
.This rule places User objects in the correct department containers depending upon what value is stored in the OU attribute. If a User object needs to be placed and has the OU attribute available, then the User object is place in the uid=unique name,ou=value of OU attribute,dest-base.
The dest-base is a local variable. The DN must be the relative root path of the department containers. It can be an organization or an organizational unit. The value stored in the OU attribute must be the name of a child container of the dest-base local variable.
The value of the OU attribute must be the name of the child container. If the OU attribute is not present, then this rule is not executed.
The uid attribute of the User object is the first two letters of the Given Name attribute plus the Surname attribute as lowercase. The rule uses LDAP format.