6.12 Matching - Subscriber Mirrored - LDAP Format

This rule finds matches in a connected system that uses LDAP format DNs for objects in the Identity Vault based on their names and locations. Implement the rule on the Subscriber Matching policy in the driver.

There are two steps involved in using the predefined rules: creating a policy in the Matching policy set, and importing the predefined rule. If you already have a Matching policy that you want to add this rule to, skip to Importing the Predefined Rule.

6.12.1 Creating a Policy

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

  2. Click the Matching Policy 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 Rule Builder is launched.

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

6.12.2 Importing the Predefined Rule

  1. In the Rule Builder, click Insert.

  2. Select Matching - Subscriber Mirrored - LDAP format.

    Matching - subscriber mirrored - LDAP format
  3. To edit the rule, click Matching - Subscriber Mirrored - LDAP format in the Rule Builder.

  4. Delete [Enter base of source hierarchy] from the Value.

  5. Browse to the container in the source hierarchy where you want the matching to start, then click OK.

  6. Click OK.

  7. Delete [Enter base of destination hierarchy] from the Enter String field.

  8. Click on the Edit Arguments icon to launch the Argument Builder.

  9. Select Text in the Noun list, then click Add.

  10. In the Editor, click the browse button, then browse to and select the container in the destination hierarchy where you want the source structure to be matched, then click OK.

  11. Click OK.

6.12.3 How the Rule Works

When an Add event occurs on an object in the Identity Vault that is located within the specified source subtree, the rule constructs a DN that represents the same object name and location within the connected system relative to the specified destination subtree. If the destination objects exists and is of the desired object class, then it is considered a match. You must supply the DNs of the source (Identity Vault) and destination (connected system) subtrees. The connected system must use an LDAP-formatted DN.