2018 - April

Last Month

• Review of Shibboleth UI Work and Next Steps (Unicon)
• Resourcing Discussions by EOY2018 and Beyond
  
• Must decide about naming of COmanage, when it's not used as the registry
  
• Global Summit Objectives
  • Campus Success Program F2F on Thursday
  • Trust & Identity Showcase work
  • Review Timeline and Functionality of Internet2’s implementation / Campus Success Program-driven work
    
• Implications and Clarifications re: Cloud Connect (which will become a new standing item)

This Month

• Continued review of the Shibboleth UI Work including the wrap up of MVP2 and finalized requirements for MVP3 work (Unicon)
• Planning of the conceptual requirements for the “shadow” or “test” federation to be followed by a work plan based on the Federation Manager development work
• Reviewed resource requirements for meeting work commitments to satisfy the remaining requirements for the 2018 TIER Work Plan by Thematic Grouping” (https://docs.google.com/document/d/17_WxqBrjYD2EuMJQVerdVMZ1RBtRen1CnyloMZP5YkI/edit?usp=sharing)
• Planned for the work required to set up all TIER components under sustainable maintenance
• Planning for setting up a UI "BOF" Collaboration for Components

Roadblocks

• TBD

Last Month

• • Review and develop detailed plan for Trust & Identity Showcase sessions at Global Summit
  • 1 Session Each Day
  • T&I Showcase    Campus Success Program Monday         2:45 - 4:00

  • T&I Showcase    TIER part 1 Tuesday        1:15 - 2:30

  • T&I Showcase    TIER part 2 Wednesday   8:45 - 10:00
    

  • Review work for Person Registry - Next steps
    • Finalize the schema for minimal person between Systems of Record and the Person Registry
    • API & Messaging Specifications
    • ID Match API calls
    • Event triggering
    • Plan for a TIER Registry Deployment Guide
  • Begin work on Credential Management
  • Begin supporting work with the Campus Success Program Banner Onboarding WG
  • Develop updated inventory of APIs

This Month

Roadblocks

• TBD

Last Month

• • Continued work to create logging standards. The original specification we created would not work well for all use cases. A new, more flexible specification is almost complete.
  • Completed the work to specify the midPoint container and started began preparation of documents for discussion with Evolveum.
  • Completed independent specification for how TIER-compatible containers are to be designed.
  • Continued to solicit testers/deployers for the various components.

This Month

Roadblocks

• TBD

• • We've created a Github repo for collecting SCIM schema requirements: https://github.internet2.edu/tier/scim-schema. Keith H kindly provided a JSON version of the SCIM core schema which we've added to the repo. We're currently searching for extensions but haven't found any so far. Any contributions are welcomed and should be sent to KeithWessel.
  • We completed a set of use cases for a bulk provisioning API. After reviewing these, the TIER API WG doesn't believe that such an API is necessary. They've posted their responses at the bottom of our wiki page: https://spaces.at.internet2.edu/x/koFyBw. The use cases will help to be a good exercise to test if existing TIER APIs can support them.
  • We're working on our provisioning engine evaluations which will help to guide provisioning best practices that we document.
  • Ethan and Jeff are trying out our evaluation questions by doing an evaluation of Midpoint.
  • The group is working on an evaluation process and template to guide and simplify evaluations. We'll soon be looking for community members to evaluate both open source and commercial provisioning engines. Interested volunteers should contact Keith Wessel.

• Concluded work on a far-too-long questionnaire for evaluating provisioning engines.

• Discussed with a few fellow Big Ten IDM folks, and came up with a plan for a shorter evaluation questionnaire that still meets our needs. We’re done from 150+ questions to 35: https://spaces.at.internet2.edu/x/0Q2MBw

• Results of evaluations will be combined with surveys of the Big Ten member schools from last summer to create three deliverables: a best practices write-up, a list of needed functionality that products don’t support today for consideration on the TIER roadmap, and a high-level product comparison chart for those shopping for provisioning products.

• We’ll be starting provisioning engine evaluations in the near future. We need help and welcome community participation. It’s not a big time commitment. If someone can give an hour or two in June, please contact Keith Wessel.