TIER-Data Structures and APIs Working Group Home

Subgroup 2: Friday, 15 April, 2016 at 10 am Eastern, 7 am Pacific, 3 pm UTC
- video: https://bluejeans.com/965988291/browser
Subgroup 1: Wednesday, 20 April, 2016 at 3 pm Eastern, Noon Pacific, 8 pm UTC
- video: https://bluejeans.com/439600784/browser

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

Working Group Chair: Keith Hazelton, University of Wisconsin

Page:

Instrumenting and Monitoring TIER Components--First Steps in a Long Journey —
Initial Investigations: Analysis of Grouper Logs using the Free and Open Source ELK stack (Elasticsearch, Logstash and Kibana)
Current work: Testing the ELK stack for Grouper log aggregation, exploration and visualization; The Grouper Demo Server is serving as the data source.
The ELK stack brings together
Page:
TIER API Basic Group Management Operations
—
Implemented
- TIER API look for subject 'S' in group 'G'
Page:

TIER API: Basic Person Management Operations —
TBD: Create Swagger Specification for These Operations
System of Record (SOR) Person Role Added
It is up to the Identity Registry to determine how to map the provided attributes to its internal data model.
Page:

TIER Standards and Guidelines —
Standards and guidelines that apply to all TIER Messages

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.

Page tree