TIER Entity Registry Working Group Home

Agenda for upcoming WG meetings plus meeting notes for the past ones are here: http://j.mp/1PWMCp5

Attendees are encouraged to participate in live-scribing the meetings on the above Google doc.

Email List: tier-entreg@internet2.edu

  – To subscribe, browse to  https://lists.internet2.edu/sympa/admin/tier-entreg

Working Group Chair: Warren Curry, University of Florida

Charter for the TIER Entity Registry Working Group (wiki page)

Key Deliverables for TIER R1

By April 1 (from Charter)

• Page:
  IAM Functional Model and IAM Glossary —

  IAM Functional Model: Diagram, Table and Glossary

• Page:
  TIER SoR-Registry Core Schema —

  Early draft of TIER Core Schema for Systems of Record (SoR) and Entity Registry – from Benn Oshrin

  There are no required attributes from the perspective of the Core Schema. It is up to a given protocol or implementation to determine what attributes are required, and how such status is conveyed between participants.

Narrative form

1.  Document Functional Requirements for System of Record (SoR) to the Entity Registry per the conscription pattern of enrollment.  
   1. 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.
   2. The Registry invokes a mock ID Match API operation that always returns ‘no match’
   3. The Registry creates a new mock person resource and returns a unique id to the calling SoR.  
2.  Define a minimal first iteration Registry person schema/resource 
3.  Draft a first iteration glossary of institutional processes around identity lifecycle management.  
4.  Draft fit/gap analysis between current COmanage registry functionality and this WG’s minimal, first iteration requirements.
5. Provide COmanage WG with rough definition of work required to fill in gaps in COmanage functionality

By April 2016 (from Charter)

1. Iterate on above, expanding scope of functionality covered by API and event messaging operations.

Entity Registry Requirements

• From CIFER Registry Team
• From CIFER Enrollment (Registration) Requirements
• From TIER campus surveys
• From U Florida (courtesy of Warren Curry)

Functional Model for Entity Registry and Allied Services

• Identity Registry Functional Model (Sept. 2011, CIFER)

Schema for core IAM resources

• Prior work: CIFER SOR-Registry Core Schema Specification

• Gabor’s overview: https://gist.github.com/geszes/3d4b9ff49441058db434

• Draft Based on Schema.org: https://gist.github.com/geszes/6bfd8926bded03786a63

• Clemson Authology schema: http://authology.org/doc/VaultServiceReference/vaultServiceReference.html

• Penn State Person Bio Record

• COmanage Registry Data Model

• Person Schema Comparisons: 

  • https://spaces.at.internet2.edu/display/cifer/SOR-Registry+Core+Schema+Strawman

  • https://gist.github.com/geszes/a889d023a3a26a763c6f

Member-contributed Resources

• 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