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

• Page:
  COmanage / Entity Registry Gap Analysis —

  COmanage 1.0.2 Compared to the TIER Entity Registry Requirements

• Page:
  IAM Functional Model and IAM Glossary —

  IAM Functional Model: Diagram, Table and Glossary

• Page:
  IAM Glossary of Terms —

  Access   Control	The act of   allowing access to facilities, programs, resources or services to authorized   persons (or other valid subjects), and denying unauthorized access. Access   Control requires that rules or policies be in place, that privileges be   defined, so that they can be enforced.
  Access   Management	That   part of Identity Management comprising the processes and tools used to   associate privileges with subjects in accord with the wishes of Authorities.  A   comprehensive set of tools and processes for assign and revoke access to   resource to digital identities.

• Page:
  Minimal/Thin Entity Registry —

  Internet2’s Trust and Identity in Education and Research (TIER) program provides a range of core functionality, including group and access management, single sign-on, and federation management. But peering deeper into the layer that forms the basis for Identity and Access Management (IAM) functionality, the TIER Entity Registry Working Group and the TIER Data Structures and APIs Working Group have proposed a data ecosystem required to support the TIER components. Central to this ecosystem is a well-defined strategy for the creation and use of data repositories. These repositories must be complete, flexible, and extensible. 

Narrative form

By April 2016 (from Charter)

1.  Document Functional Requirements for System of Record (SoR) to the Entity Registry  Define a minimal first iteration Registry person schema/resource 
2.  Draft a first iteration functional model for IAM with a glossary of institutional processes around identity lifecycle management.  
3.  Draft fit/gap analysis between current COmanage registry functionality and this WG’s Entity Registry requirements.
4. Provide COmanage Team with rough definition of work required to fill gaps in COmanage functionality

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