Date: Fri, 29 Mar 2024 12:39:34 +0000 (UTC) Message-ID: <998398583.7957.1711715974231@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_7956_875885486.1711715974231" ------=_Part_7956_875885486.1711715974231 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
InCommon TAC 2020 Work Plan
This is final version of the InCommon Technical Advisory Committee's 202= 0 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 tit= le and brief high-level description.
Alternatively, if you would like to comment on any of the existi= ng 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 c= omfortable using the wiki editor, enter it in the comments at the bottom of= the page.
The areas under consideration (and detailed below) are:
The TAC=E2=80=99s 2020 work plan is a synergistic portfolio of items wit= h two overarching themes:
There is much overlap among the items, such that working on one item wil= l result in momentum and progress on several other items.
IdP as a Service
Chartered in March of 2019 and chaired by TAC member Mary McKee (Duke) a= nd E.J. Monti (Duquesne), the IdPaaS Working Group worked on gathering info= rmation on existing solutions and defining technical and operational requir= ements that an InCommon-run IdP must meet. Besides service requirements, ot= her recommendations included criteria for feature levels, models for the re= sponsibility for meeting the requirements of running a service among involv= ed parties.
Status: draft of final report in progress
Test federation
A sandbox for the community in the form of a test federation is needed t= o provide speed and agility in trying out solutions. It could also serve as= a demonstration tool, perhaps incorporating different uses cases for diffe= rent segments that might help increase people=E2=80=99s interest in federat= ion. Features of a test federation would likely include a number of the rec= ommendations from the TAC-sponsored Deployment Profile and Streamlining SP = Onboarding Working Group
Status: drafting of charter in progress. Launching of w= orking group currently on hold due to shifting priorities caused by COVID-1= 9.
Cloud Services Cookbook update
The Committee on Institutional Collaboration, now the BTAA, worked on th= e Cloud Services Cookbook about six years ago to figure out the standard th= ings that we can ask cloud providers to do to integrate properly with InCom= mon. The landscape has changed and an update is needed. Updating the cookbo= ok is on both the TAC=E2=80=99s and the REFEDS 2020 work plan.
Deployment Profile work recommendations
The Deployment Profile Working Group created a major revision to SAML2in= t, the SAML 2.0 deployment profile, which addressed the issue of unique use= r identifiers by creating two new pairwise user identifiers to supersede ex= isting attributes. The TAC accepted the group=E2=80=99s final report and re= commendations in March of 2019 and Kantara reviewed and ratified the revise= d profile. The recommendations included changing encryption algorithms, ado= ption of the new identifiers, SAML 2.1. The TAC will be evaluating the prio= rity and meaning of the recommendations to InCommon. Some of the recommenda= tions will likely be included in a test federation and subsequent iteration= s of Baseline Expectations.
Status: strategizing in progress
Seamless Access evaluation
Seamless Access builds on the guidelines from RA21. It is a collaborativ= e initiative working to improve how library subscription content from publi= shers is accessed by promoting federated identity and accompanying technolo= gies to move away from IP-based access. The TAC will be evaluating SA to ma= ke a clear decision about what it is InCommon needs to do. This could be a = testbed and the work would include a community review. See the May 2020 IAM Online on Simplifying Federated Access to Scholarly Content and Services an= d The Scholarly Kitchen post, 'Guest Post =E2=80=93 Sea= mless Remote Access During a Global Pandemic: An Indispensable Necessity' for background.
Status: monitoring
High-level description of new work item.
Suggestion/Action = Item | Comments or Elabor= ation | Name, Organization= |
---|---|---|