Formerly the TIER-Data Structures and APIs Working Group Home
| Note | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Every other Wednesday at 3 pm Eastern, Noon Pacific, 8 pm UT Future Calls: Chose the one (Wed. or Fri.) that works best for your schedule and time zone):Friday 19 January 2018, Alternating Fridays at 10 am Eastern, 7 am Pacific, 3 pm London, 4 pm Amsterdam Wednesday, 17 January 2018, at 3 pm Eastern, Noon Pacific, 8 pm UTC
Current agenda and scribed notesAgenda and Collaborative scribing notes starting Sept 22, 2017 are HEREAttendees are encouraged to participate in live-scribing the meetings on the above Google doc Archive of older meeting notes:Up to Sept. 20 2017 http://j.mp/apiRegWG-5up to April 19 2017 http://bit.ly/tierApiReg up to 18 January 2017: http://j.mp/1PWMCp5 Email List:tierinctrust-api@internet2si@incommon.eduorg– To subscribe, browse to https://lists.internet2incommon.eduorg/sympa/subscribe/tierinctrust-apisi |
Working Group ChairChairs: Keith Hazelton, University of Wisconsin, Internet2, Ethan Kromhout, UNC Chapel Hill
Charter for Data Structures and APIs Working Group (Original Charter from TIER Initiative)
TIER Timeline and Deliverables for TechEx 2017
...
Key Deliverables from TIER Release 1
TIER API: Basic Group Management Operations
TIER API: Basic Person Management Operations
Instrumenting and Monitoring TIER Components
Narrative Form: Deliverables in the WG Charter
By April 2016
- Publish and promote the adoption of a first-round set of conventions for API and data structure design. The goal is to inform and hopefully influence API development for Release 1.0 Grouper and COmanage components.
- Pair the basic group and membership management APIs with an event-driven messaging approach to the same functionality. Clarify the circumstances that favor one approach over the other.
- Assess possible models for APIs and data structures around consent.
- Document the first round requirements for administering and monitoring IAM infrastructure and specify the kinds of instrumentation needed in each component to support administration and monitoring.
...
Inventory of TIER APIs
- Credential Management (openapi)
- Used to manage credentials for a Person or Entity
- Group Registry (openapi)
- Used for Group and Group Member related requests
- SCIM (+ extensions?)
- ID Match (openapi)
- Used by Registry or SORs to obtain a Reference ID based on (SOR) attributes
- Person Registry (openapi)
- Used for Person (and maybe other Entity?) related API requests
- SCIM (+ extensions)
- Subscriber Message Notification (openapi)
- Used to send update notifications to downstream systems
Schema work items
- Under the API-Schema organization on Internet2 Enterprise Github
Older items
Jim Fox on Messaging at U Dub
Rob Carter thoughts on fine-grained authZ on APIs for data access <== relates to issues discussed on the 11 December 2015 call
JIRA Project for TIER API Working Group Working Group Members Representing Stakeholder Interests
Background information on TIER, Internet2 initiative on Trust and Identity in Education and Research
- Internet2 Middleware IAM Diagram from 2006.
- Accomplishments and Plans from the TIER API and Registries Working Groups (blog January 2017)
...