Duplicate Management

Duplicate Enrollments can happen a number of ways, and there is no single technique to prevent them from happening. There are, however, a few options to reduce the likelihood of a duplicate enrollment happening. We will not review duplicate management in depth in this workshop, though we can talk about the processes more toward the end of the workshop if there is time and interest.

To understand how to clean up a Duplicate Enrollment, see Resolving Enrollment Issues.

  • For administrator and invitation based enrollments, use Advisory Identity Matching. Administrators should check for matching existing CO People before completing the enrollment flow.
  • For self signup based enrollments, Require Confirmation of Email and Require Enrollee Authentication. If a new Petition matches an existing Identity, automatic linking may take place.
    • Additional changes to catch duplicate self signup enrollments are planned. (CO-1088)
  • For Pipeline based synchronization from Organizational Identity Sources, various Match Strategies are available.

D. Identity Matching during enrollment workflows

How identities are matched for this enrollment flow. For this type of enrollment workflow, set this to “Self”. for invitation enrollment flow, recommend using “Advisory.”

COmanage Registry can perform identity matching when enrollment is performed. This is the process of checking for existing CO People that might match the person being enrolled. Note that matching only happens during the execution of an enrollment flow, now when manually adding a new CO Person. The following matching policies are available:

  • None: No matching is performed.
  • Advisory: Potential matches are identified, but Registry does not take any action. See more on Advisory Matching, below. This should only be enabled for Administrator (or other trusted user) driven enrollments. Advisory matching currently only works when the following conditions are met:
    1. Advisory matching is configured for the enrollment flow.
    2. The field where data is entered is either a given or family name field.

    If an enrollment flow is configured to collect more than one type of name, only the first set of name fields emitted will be enabled for Advisory Matching.

    1. At least 3 characters are entered into the field.
  • Automatic: If highly likely matches are found, Registry automatically links the Enrollee to the existing CO Person. If probable matches are found, the Petitioner is given an opportunity to select one. This option is not currently implemented. (CO-298)
  • Select: The Petitioner chooses an existing CO Person from the list of all CO People. This is useful for additional role enrollment, and should only be enabled for Administrator (or other trusted user) driven enrollments.
  • Self: The new enrollment is automatically linked to the Petitioner. Used for self service account linking and additional role enrollment. For Self matching, at least one of J. Require Enrollee Authentication, F. Require Confirmation of Email, or E. Require Approval for Enrollment must be enabled in order for the enrollment to proceed from Pending Approval status to Active.

Copyright (C) 2018-2020 University Corporation for Advanced Internet Development (Internet2) - All Rights Reserved