6.15 Placement - Subscriber Mirrored - LDAP Format

This rule places objects in the data store by using the mirrored structure in the Identity Vault from a specified point. 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.

6.15.1 Creating a Policy

  1. Open the Identity Manager Driver Overview for the driver you want to manage.

    For instructions on how to access the Identity Manager Driver Overview page, see Accessing the Identity Manager Driver Overview Page.

  2. Click the Placement Policies set object on the Subscriber channel.

  3. Click Insert.

  4. Name the policy, make sure to implement the policy with the Policy Builder, then click OK.

    The Policy Builder is launched.

  5. Continue with Section 6.15.2, Importing the Predefined Rule.

6.15.2 Importing the Predefined Rule

  1. In the Policy Builder, click Insert.

  2. Select Placement - Subscriber Mirrored - LDAP Format.

  3. Expand the predefined rule.

    Placement - subscriber mirrored - LDAP format

  4. To edit the rule, click Placement - Subscriber Mirrored - LDAP Format in the Policy Builder.

    The Rule Builder is launched.

  5. In the Value field, browse to and click the container in the source hierarchy where you want the object to be acted upon.

  6. Click the Edit the arguments icon next to the Enter string field.

    The Argument Builder is launched.

  7. In the Editor, click the browse button, browse to and select the container in the destination hierarchy where you want the object to be placed, then click OK.

  8. Click OK.

6.15.3 How the Rule Works

If the User object resides in the specified source subtree, the object is placed at the same relative name and location within the Identity Vault. You must supply the DNs of the source (Identity Vault) and destination (connected system) subtrees. The connected system must use an LDAP-formatted DN.