InCommon TAC 2019 Work Plan
InCommon TAC 2019 Work Plan
This is final version of the InCommon Technical Advisory Committee's 2019 work plan. The TAC provides recommendations related to the technical operation and management of InCommon. The work plan outlines the proposed technical priorities, particularly for the InCommon Federation.
If you have a new work item to propose, please copy the Template below and paste at the bottom of the work items, filling in a title and brief high-level description.
Alternatively, if you would like to comment on any of the existing items, please add a comment to the wiki page. Note that you need to sign into Confluence in order to edit or leave a comment.
Lastly, if you have a work item you'd like to propose but aren't comfortable using the wiki editor, enter it in the comments at the bottom of the page.
The areas under consideration (and detailed below) are:
2019 First Half
Working Groups
- IdP as a Service (IdPaaS) Working Group
Community requirements gathering and recommendations for an InCommon-branded hosted solution
Will likely help with the Long Tail and R&S
Requires participation by cohorts that don’t usually participate
Vendors will be involved
- Wiki space with charter and list info
Federation 2.0 (REFEDS) Working Group
TAC member Judith Bush (OCLC) is co-chair
- OIDC/OAuth Deployment Working Group
Other Work Items
RA21
Assess the “fit” of an InCommon-run IdP discovery persistence service
- Update 5/16: GEANT will be hosting a beta service; circle back when beta launches
FIM4R Recommendations for InCommon
Invest in Areas to Support Collaboration-as-a-Service
Increase Focus on Sustainability Practices
Increase Research Representation in All Levels of FIM Governance
Responding to the requirements of researchers, a key audience
Will help with IdPs not providing attributes to R&S SPs
IdPaaS might meet some of the recommendations
Collaboration with CACTI/CTAB
Representatives (not chairs) to attend meetings
- Update 5/16: completed
2019 Second Half
The work items for the second half of 2019 are:
Follow up to the Streamlining SP Onboarding Working GroupFollow up to the Attributes for Collaboration and Federation Working GroupThe TAC is reviewing the draft of InCommon’s response to the above two groups through February- Update 5/23: The recommendations the above two working groups made are planned or underway InCommon work items
Follow up after hiatus and Kantara ratification of revised SAML2int
Create an R&E specific profile to layer on top of SAML2intUpdate 5/23: Likely kick-off in September/October- Update 9/19: Item moved to draft 2020 plan
- Might factor into Baseline, badging, automated testing
Development of a test InCommon federationWorking group to be chartered for requirements gathering late or early 2020- Update 9/19: Item moved to draft 2020 plan
- Badging for Participants and maturity model outline for adoption of federation technologies and protocols
- Update 5/23: A sub-group with members of CTAB and TAC is working on this
- Address new TAC member onboarding and communication gaps
Parking Lot
SAML SP front end
SPs that don’t play nice with InCommon and SAML
Might get addressed later in Federation 2.0
ADFS as an IdP
Requirements gathering, centralizing documentation, potentially working with Microsoft to implement changes/requirements
IdPaaS work could make this moot
In the spring, CAF and SWAMID starting using ADFSToolkit, which augments ADFS
(Template for New Proposed Work Item)
High-level description of new work item.
Suggestion/Action Item | Comments or Elaboration | Name, Organization |