Back to TIER Entity Registry Wiki Home Page
TIER Entity Registry Working Group
Charter for Phase I
Problem Description
The ‘glue’ that binds IAM services together is an Entity Registry. Such a Registry facilitates the creation, maintenance, and distribution of person and other subject / entity information across TIER components and other elements of the institutional IT landscape. It must be capable of receiving, deduplicating, resolving collisions and otherwise grooming this information from authoritative sources and disseminating canonical person and other entity information to downstream services as a data hub or replication source.
...
The TIER Entity Registry Phase I Working Group is tasked with identifying and documenting the minimum viable requirements for a TIER Registry component and making recommendations to the TIER Community Architecture Planning and Engagement (CAPE) group about the criteria for the adoption of an official TIER Registry component. This set of recommendations will then be used to guide the relevant API, development and packaging work.
Stakeholders, Influencers and Influences
Different audiences will need to be invited to engage on different aspects of this work. It will be important for team members to bring the perspective and represent the interests of at least the following stakeholder groups:
IAM software component designers and developers
Campus IAM and security service providers
Campus integration teams
Application developers
Membership
Any interested member of the community may participate in the activity of the group. Members self-select by subscribing to the group mailing list and contributing during group calls and in discussions on the WG mailing list.
Selection of Chair
The chair will be selected by the TIER Ad Hoc Advisory group from the membership of the group. Warren Curry of the University of Florida has been nominated.
Deliverables
The group should complete its first version of the following Phase I items no later than April 1, 2016.
...
Determine gaps between COmanage’s registry and the minimal, first iteration requirements for the TIER Entity Registry. Recommend to CAPE that development work be commissioned to fill those gaps.
Timeline
Iteration 1 (Monday, February 1 to Friday, March 4, 2016)
...
Repeat steps 1) to 4) above, expanding the scope of functionality covered by API and event messaging operations.
Phase I Wrap-Up
After completion of the above tasks and deliverables, this Working Group should help draft a charter for a follow-on Phase II Entity Registry Working Group charged with determining a richer set of functionality for the Entity Registry Component of TIER. Phase II work should also identify gaps, document resource needs and outline a roadmap for implementing expanded functionality in future releases of the TIER Entity Registry package.
Request for Internet2 Assistance:
Already completed
Creation of a WG Wiki space
Creation and archiving of a WG mailing list TIER-entreg@internet2.edu
NOTE: For now, we will use the TIER-API@internet2.edu list
Set up BlueJeans for WG meetings
Set up an issue tracking service using JIRA
JIRA Kanban Board has been created (SZoppi)
Project Owner: Warren Curry (whcurry@ufl.edu)
https://bugs.internet2.edu/jira/plugins/servlet/project-config/TER
Creation of calendar invitation (Google calendar, Outlook, Office 365).
Ongoing assistance
Funding to offset time and work being done by external subject matter experts
Propose and send out agendas and meeting reminders
Arrange for TIER developers, QA people, and others to allocate some of their time to working together with this WG as specified under "Tasks" above
See Also
- TIER Entity Registry Wiki Home Page
- TIER Working Groups Home
- TIER Data Structures and APIs Working Group
- Background information on TIER, the Internet2 initiative on Trust and Identity in Education and Research