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.

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

  2. Click the Matching Policy 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.12.2, Importing the Predefined Rule.

6.12.2 Importing the Predefined Rule

  1. In the Policy Builder, click Insert.

    For information on how to access the policy builder, see Accessing the Policy Builder.

  2. Select Matching - Subscriber Mirrored - LDAP format.

  3. Expand the predefined rule.

    Matching - subscriber mirrored - LDAP format

  4. To edit the rule, click Matching - Subscriber Mirrored - LDAP format in the Policy Builder.

    The Rule Builder is launched.

  5. In the Condition section, click the Browse icon next to the Value field.

  6. Click the container in the source hierarchy where you want the matching to start.

  7. In the Actions section, click the Edit the arguments icon next to the Enter string field.

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

  9. 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.