InCommon Steering Committee Meeting - June 8, 2020


Minutes

Attending: Ted Hanss, Laura Paglione, Dave Robinson, Brad Christ, Marc Wallman, Christine Miki, Sean Reynolds, Chris Sedore, Michael Berman

With: Dean Woodbeck, Kevin Morooney, David Bantz, Von Welch, Kevin Morooney, Jessica FInk, Janemarie Duh, Steve Zoppi

BaseCAMP

  • First one held last summer
  • Prequel to CAMP and ACAMP
  • Response to “make the tent bigger” and create an onramp for those new to the field
  • About 70 people last year - mostly newcomers
  • Moved to virtual with a fee structure

InCommon Trusted Access Platform

Steve Zoppi provided an overview and update on the InCommon Trusted Access Platform.

  1. Software Development Building Blocks
    1. Contributors include campus, volunteer developers, independent contractors, agency partners, international federations and consortia
    2. Community components (Shibboleth, COmanage, Grouper), InCommon glue (like Federation), Complementary projects (like Docker), Internet2 CI-CD (packaging and containerization and quality assurance)
    3. Internet2 CI-CD (Continuous Improvement/Continuous Development) packaging and QA
    1. Requirements and enhancement requests
    2. Software development and architecture
    3. Deployment and training
  2. Ongoing Mission (Program) Principles
  3. The Reference Architecture (Services)
    1. LDAP, SQL, CSV import/export, more
    1. COmanage, midPoint
    1. Initiation points through COmanage, Grouper, midPoint
    1. Multilateral InCommon federation friendly (pre-configuration)
    2. Bilateral services
    3. eduGAIN
    1. Identity sources
    2. Registry services
    3. Complex group management services (Grouper)
    4. Authentication and Federation services (Shib, InCommon Federation Manager and metadata distribution)
    5. Provisioning and DeProvisioning services
    6. Identity consumers
  4. The Component Pipeline (Deconstructing the Services Architecture)
    1. Concern with integrating the open-source tools, so specified interconnection and interoperation tools (RabbitMQ, LDAP, MariaDB/MySQL)
    2. Simplified deployment by containerizing software
    3. Continuous integration pipeline - containers are updated as changes are made
  5. Governance and Evolution
    1. Community advisory and working groups are active (9 in all) with continuous input, so continuous course correction. Multi-channel communication (email, Slack, conference calls)
    2. Manage the work through a public Jira board (backlog, active work, next release)
    3. General pipeline is Backlog => To Do => In Progress => Done => Release
    4. Project submissions come through various sources and will hire consultants and contractors to do priority work, which helps speed up the pipeline
    5. Non-technical expansion is done through CSP, Component training, Webinars and presentations
  6. Community Enrichment

Learn more: Platform library: https://spaces.at.internet2.edu/display/ITAP

Kevin noted that the platform has come a long way since the TIER program started five years ago. The components are connected, there is a sustainable funding and development model, and there is a combination of staff, community, and independent consultants available to work on priorities. We are finding, through schools that participate in the Collaboration Success Program (just finishing its second year) that they are adopting the software because it is relevant, sustainable, and viable, with a predictable cadence and funding.

Coming Up

  • Wednesday, June 10 (2 pm ET): IAM Online, "Hiring for IAM" (incommon.org/iamonline)
  • July - discuss recruiting for Steering next year
  • July - stories we want to tell
  • August - conversation about workforce needs

Next Meeting - July 6, 2020

4 pm ET / 3 pm CT / 2 pm MT / 1 pm PT


  • No labels