DRAFT - DRAFT- DRAFT
TIER Registry and DATA and API workgroups have provided an ID Match POC in September 2017 This followed work done in earlier projects and Benn Oshrin brought this out for demo purposes. During December and January of 2018 refinement of a proposed architecture and of the POC ID Match has been underway. Calling structures to the RESTFUL API and discussions on how it can fit into the TIER Entity Registry - Identity OnBoarding process.
An architecture diagram TIER ENTITY REGISTRY - Identity OnBoarding diagram and event discussion can be found at
******* insert here ********
The
The intent of this document is to indicate in a high level sense how to align ID Match in your institutions processes. It is intended to describe a pattern for institutions to use when building a Registry Onboarding process.
The ID Match is a restful API that can be called in many architectural patterns and or sources. The workgroups have discussed over several iteration and about 2.5 months and suggest calling ID Match component from the "Registry Update Controller" shown within the Identity OnBoarding flow.
Step-by-step guide
Determine your initial System of Record(s) (SOR) to be onboarded or interfaced into your entity registry.
Map the attributes in your SOR into the normalized TIER information structure
- This structure will reflect the TIER minimal registry structure plus any additional person attributes or extensions you desire to store in your registry.
- The TIER registry working group encourages you to maintain only data needed for access management in the registry. OF course you may extend as needed of course.
- It is intended that in Entities other than people will be accommodated by the registry. Additional entities beyond person are intended to be added in later work. There are proposed structures for application entities in early stages of design.
- Attributes are normalized into a consistent form so that
Related articles