TIER Technical Working Groups News
TIER Registries Working Group
The TIER Entity Registry Working Group was spun off from the TIER Data Structures and APIs Working Group with the intention to identify and document the minimum viable requirements for a TIER Registry component and to make recommendations about the criteria for the adoption of an official TIER Registry component. The set of recommendations generated by the group will then be used to guide API, development, and packaging work.
Warren Curry (University of Florida) agreed to chair the TIER Entity Registry working group, which held its first call on February 10 and will continue to meet twice a week. The group’s charter can be viewed here. Community members interested in assisting with this effort are encouraged to subscribe the group’s mailing list here.
TIER Packaging Working Group
Based on analysis of the TIER packaging survey, the TIER Packaging Working Group has identified adoption of Docker containers as a key direction for the TIER packaging work. While Docker was indicated as one of the most desirable solutions, many campuses responded that they lacked adequate expertise with Docker containers. The majority of campuses indicated they are currently running on some mix of physical servers, VMs, and/or virtual appliance. Only 9% are running Docker now, but most expect to be doing so within the next 1-2 years. As Jim Jokl, University of Virginia, the TIER Packaging Working Group chair, stated: “Our survey showed a low level of comfort with Docker containers now but also displayed a growing expectation that campus use of Docker would grow over the timeframe of TIER development. Using a Docker-centric approach now likely means that TIER will need to provide both the containers themselves and a preconfigured run environment so that campuses don’t need Docker expertise to deploy TIER components.”
The full TIER Packaging survey results are available in a variety of formats, and offer an interesting snapshot of not only the desired outcomes for TIER’s components but the state of identity management on the campuses today.
TIER Data Structures and APIs Working Group
In addition to creating the TIER Entity Registry Working Group (as detailed above), the Data Structures and APIs Working Group, chaired by Keith Hazelton, University of Wisconsin, has begun work on specifications for a set of the most common and useful management operations of its API. In defining these operations, the group drew from its native technical expertise and studied use cases from other campuses. The TIER packaging survey also informed decisions about the functionality and dependent components of the API.
TIER Security and Audit Working Group
The Security and Audit Working Group, under the leadership of Helen Patton, The Ohio State University, completed its operational charter and a work plan for the coming year, which was approved by the TIER Ad Hoc Advisory Group. The working group has also recruited subject matter experts, including community members with knowledge of regulatory compliance and those who have experience with other auditing processes around IdM. Also, meetings have moved from monthly to bi-weekly. The charter can be viewed here.
TIER Component Architects Group
The TIER Component Architects Group is moving into the next phase of collaboration with the API and Data Structures team. The latest topic is that of “instrumentation” for performance and utilization statistics as well as for operational monitoring. Keith Hazelton and the API team have begun discussions designed to answer questions of import arising from the broader adoption of the components. As functionality is added to each component, we will want to enable campus operations and IAM Architects (as well as the TIER development teams themselves) to understand whether or not that functionality is being utilized and how broadly. Based on that, development team resources may be redirected to higher priority projects and away from unused or underused functionality. Since the components will need to evolve over time, “hard numbers” of this kind will provide the most reliable guide to what our next steps should be as a community.
The TIER Component Architects Group is now holding weekly meetings to ramp up collaboration in preparation for the first release of TIER. The group focuses on aligning TIER processes, including the common core of technology platforms and tools. Steve Zoppi (Internet2) leads the group. Component architects include Scott Cantor, Ohio State University (Shibboleth); Chris Hyzer, University of Pennsylvania (Grouper); Benn Oshrin, Spherical Cow Group (COmanage); Ken Klingenstein, Internet2 (Consent); and Nick Roy, Internet2 (InCommon).