TIER Entity Registry Working Group Home
| Note |
|---|
Call Schedule
|
| Note |
Future Calls: Chose the one (Wed. or Fri.) that works best for your schedule and time zone):
|
Agenda for upcoming WG meetings plus meeting notes for the past ones are here: http://j.mp/1PWMCp5
...
– To subscribe, browse to https://lists.internet2.edu/sympa/admin/tier-entreg
Working Group ChairCo-Chairs: Warren Curry, University of Florida and Benn Oshrin, Spherical Cow Group
Charter for the TIER Entity Registry Working Group
...
MidPoint as Entity Registry: Investigation and Evaluation
| Include Page | ||||
|---|---|---|---|---|
|
TIER Entity Registry Update - 2017 GLobal Summit
TIER Identity Data Ecosystem2col.pdf
TIER Application View Integration Layer Concept of Person Maintenance and Retrieval (Draft)
whc, 11/07/2017
- For use by SORs to retrieve and maintain information related to a person entity.
- For use by any consumer application to acquire information related to a person entity
- 2017 Tech Ex Summary - Registry Summary techex 102017.pdf
- Diagram
| View file | ||||
|---|---|---|---|---|
|
- Application that is an SOR needs to indicate to the Identity System there is a new or changed person
- It would invoke the Maintain Person logic that encapsulates the (Minimal registry, Affiliation and perhaps other groups, and other person data that the institution has defined beyond the minimal registry)
- The service: validate the use of the service by the calling party/application
- Person Schema (encapsulated version)
- The service maps the data from the encapsulated schema into three subsets:
- registry
- groups
- person detail
- The service call the Registry rest call (Ethan K demo work)
- The service call the Group rest call (grouper API)
- The service call the Institution supplied Person rest call (need a sample)
Key Deliverables from TIER Release 1
Requirements on an Entity Registry and Related Components
COmanage / Entity Registry Gap Analysis
IAM Functional Model and IAM Glossary
TIER Core Schema for Systems of Record and Entity Registry - Early Draft
Narrative Form: Deliverables in the WG Charter
...
Key Deliverables for TIER R1
By March 4 (from Charter)
- Document Functional Requirements for System of Record (SoR) to the Entity Registry per the conscription pattern of enrollment.
- In the conscription pattern of enrollment, person resources are created/mastered in the Registry; an SoR sends the Registry a representation of a person resource that is new to them.
- The Registry invokes a mock ID Match API operation that always returns ‘no match’
- The Registry creates a new mock person resource and returns a unique id to the calling SoR.
- Document operations on person resources to be exposed as APIs and as event messages for the above connections, SoR to Registry and Registry to IDMatch;
- Document Functional Requirements for System of Record (SoR) to the Entity Registry
- Define a minimal first iteration Registry person schema/resource
- Draft a first iteration glossary functional model for IAM with a glossary of institutional processes around identity lifecycle management .
- Draft fit/gap analysis between current COmanage registry functionality and this WG’s minimal, first iteration Entity Registry requirements .
- Provide COmanage WG Team with rough definition of work required to fill in gaps in COmanage functionality
...
Iterate on above, expanding scope of functionality covered by API and event messaging operations.
...
Entity Registry Requirements
- From CIFER Registry Team
- From CIFER CIFER Enrollment (Registration) Requirements
- From TIER campus surveys
- From U Florida (courtesy of Warren Curry)
...
- University of Wisconsin - UDS Person Schema
- Comparison of UW-Madison UDS Person API and CIFER API
- Rob Carter thoughts on fine-grained authZ on APIs for data access
...
See Also :
- TIER Working Groups Home
- TIER Data Structures and APIs Working Group
- Background information on TIER , Internet2 initiative on Trust and Identity in Education and Research
...