Uploaded image for project: 'COmanage'
  1. COmanage
  2. CO-1796

Create Enrollment Flow Duplicate Check Step

    XMLWordPrintable

Details

    Description

      Create a new duplicate_check Enrollment Flow step and refactor existing logic from CoPetition::collectIdentifier into it. This new step would run after collectIdentifier.

      Depending on the Enrollment Flow configuration, duplicate checks would be performed based on

      1. Identifier ($REMOTE_USER) or perhaps more flexibly based on a specified identifier type. This would replace existing functionality.
      2. Verified EmailAddress (CO-1522).
      3. Call out to Match API.

      When support for Match API is added (not in scope for this ticket, maybe part of CO-298), duplicate_check needs to be able to handle a fuzzy match (API return code 300), probably by rendering a view with the possible candidates.

      Attachments

        Issue Links

          Activity

            People

              arlen.johnson@at.internet2.edu Arlen Johnson (google.com)
              benn.oshrin@at.internet2.edu Benn Oshrin (internet2.edu)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: