Identity Matching refers to the task of determining if a person presented by a System of Record (SoR) is already known to the Identity Management System (IdMS). There are several characteristics of an Identity Matching implementation.
In a coordinated implementation, all Systems of Record agree to a single set of "golden" attributes, and the Identity Matching component is authoritative for these attributes. When an SoR presents attributes for matching, the Identity Matching component matches against the single, golden set of attributes.
In an independent implementation, each system of record is authoritative for all of its own attributes. When an SoR presents attributes for matching, the Identity Matching component may match against a canonical representation of these attributes as managed by the IdMS, but it may also match against each SoR's representation of these attributes.
When a partial/potential match occurs, the client may be able to resolve the match synchronously by presenting information to the data entry personnel and submitting a forced resolution request.
If the client is not able to do so, then the match is resolved asynchronously, usually by a notification going to a match administrator, who can then view the potential match and resolve it.
When matching is performed via batch operations, it must be asynchronous.
Identity Matching can be performed at the Person Registry or as a standalone service.
Identity Matching can be performed before a record is added to the Person Registry, or at the Person Registry. In either case, the Identity Matching might be performed by the Person Registry, or by a standalone service.
COmanage Match is a standalone Identity Matching solution based on the ID Match Strawman API. It can work with, but does not require the use of, COmanage Registry.