...
When using COmanage Match, it is not possible to use the same SOR Label for both Pipelines and Enrollment Flows, since Pipelines require External resolution and Enrollment Flow require Interactive resolution.
Match Servers
To define a Match Server, go to Registry > Servers > 
Add a New Server. Set the server type to Match.
...
See also: COmanage Match Attributes
Enrollment Flow Configuration
| Info |
|---|
Currently, Match integration is only recommended for administrator driven enrollment flows, ie those where Petitioner Enrollment Authorization is set to CO Admin or COU Admin. In particular, Match integration is not suitable for use with Self Signup flows. (CO-2317) This is due to the possibility that a match request will generate possible matches that must be reviewed before a Reference Identifier can be assigned. The only currently process supported within Enrollment Flows for potential match resolution is interactive, and in most scenarios it is a security risk to allow a self signup user to select their own match resolution. Additionally, Email Addresses need not be verified for match requests. |
- Configure the Enrollment Flow with Identity Matching set to External. Select the appropriate Match Server from the list provided.
- Make sure the Enrollment Attributes collected include CO Person attributes with the same configuration (including types, if appropriate) as the Match Server Attributes.
- Set Duplicate Enrollment Mode to an appropriate configuration.
- For Registry v4.1.0 and later, define the System of Record Label.
Handling Fuzzy Matches
If the match request is inconclusive, a list of potential candidates will be displayed as part of the Enrollment Flow. To link to an existing record, select the appropriate Reference Identifier. To create a new Reference Identifier, select "New".
When connected to COmanage Match, the SOR should be configured with a Resolution Mode of Interactive.
Updating Match Attributes
Updating Match Attributes for Match Requests created by Enrollment Flows is not currently supported. (CO-2318)
Organizational Identity Source Configuration
- For Registry v4.1.0 and later, define the System of Record Label.
- Attach a Pipeline to the OIS with a Match Strategy of External, and select the appropriate Match Server, defined above.
Handling Fuzzy Matches
If the match request is inconclusive, the Pipeline will fail. An administrator must login to the Match server and resolve the conflict. On the next attempt to process the Pipeline, the Reference ID will be obtained and processing will complete. Alternately, if the inconclusive result was caused by bad data in the SOR record, the record can be corrected and will be successfully processed on the next execution of the Pipeline.
When connected to COmanage Match, the SOR should be configured with a Resolution Mode of External.
Updating Match Attributes
Once a Reference Identifier is assigned, if the underlying OIS record is changed (eg: if the person's name is updated in the upstream data source) no automatic rematching will take place. However, an Update Match Attributes request will be sent to the Match server, so that the Match server has the latest attributes for future matching operations.
Currently, records are never removed from the Match server, even after an expunge from Registry.
Match Resolution Notification Configuration
As of v4.1.0, Registry supports Match's Match Resolution Endpoint Notification Protocol via the Match Callback Core API.
...