Refining the Registry Update Controller Process
DRAFT
TIER Registry and DATA and API workgroups have provided an ID Match POC in September 2017. This followed was work done in earlier projects and Benn Oshrin brought this out for demo purposes. During December 2017 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 regarding how it fits into the TIER Entity Registry - Identity OnBoarding process. Availability of this is proposed ID Match component is projected to be during March 2018.
...
The ID Match is a restful API that can be called in many architectural patterns and or sources. The Registry and API workgroups discussed patterns over several iterations and about 2.5 months have concluded with a suggestion as follows. Calling ID Match component from the "Registry Update Controller" shown within the Identity OnBoarding flow.
Considerations about ID Match
A simple manner to think about your identity system data flows can be considered in two fundamental flows, Identity Onboarding and Identity Provisioning and Authorization. Simply processes to get data into the ecosystem and processes to get data downstream or out to the applications relying on the access management services.
...
| Gliffy Diagram | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Step-by-step guide
Determine your initial System of Record(s) (SOR) to be onboarded or interfaced into your entity registry.
...
There are more steps (7 thru 11 from the identity onboarding flow architecture) to consider related to the Identity Onboarding, however since this document is focusing on the ID Match they are not covered here. The Credential Management controller and the Groups Update Controller are treated in separate confluence documents.
| Info |
|---|
Related articles
| Content by Label | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...