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: |
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
Federation 2.0 (REFEDS) Working Group
TAC member Judith Bush (OCLC) is co-chair
RA21
Assess the “fit” of an InCommon-run IdP discovery persistence service
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
The work items for the second half of 2019 are:
Follow up to the Streamlining SP Onboarding Working Group
Follow up to the Attributes for Collaboration and Federation Working Group
The TAC is reviewing the draft of InCommon’s response to the above two groups through February
Follow up after hiatus and Kantara ratification of revised SAML2int
Create an R&E specific profile to layer on top of SAML2int
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
High-level description of new work item.
Suggestion/Action Item | Comments or Elaboration | Name, Organization |