Versions Compared

Old Version 9

changes.mady.by.user Albert Wu (internet2.edu)

Saved on

compared with

New Version 10

changes.mady.by.user Janemarie Duh

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. IdP as a Service (IdPaaS) Working Group

    1. Community requirements gathering and recommendations for an InCommon-branded hosted solution

    2. Will likely help with the Long Tail and R&S

    3. Requires participation by cohorts that don’t usually participate

    4. Vendors will be involved

    5. Wiki space with charter and list info

  2. Federation 2.0 (REFEDS) Working Group

    1. TAC

    3. participationTAC

    1. member Judith Bush (OCLC) is co-chair

    1. TAC participation

    2. Wiki and meeting notes

  4. OIDC/OAuth Deployment Working Group

...

  1. RA21

    1. Assess the “fit” of an InCommon-run IdP discovery persistence service

    2. (update Update 5/16): GEANT will be hosting a beta service; circle back when beta launches.

  2. FIM4R Recommendations for InCommon

  3. Responding to the requirements of researchers, a key audience

    1. Invest in Areas to Support Collaboration-as-a-Service

    2. Increase Focus on Sustainability Practices

    3. Increase Research Representation in All Levels of FIM Governance

    1. Responding to the requirements of researchers, a key audience

    2. Will help with IdPs not providing attributes to R&S SPs

    3. IdPaaS might meet some of the recommendations

  5. Collaboration with CACTI/CTAB

    1. Representatives (not chairs) to attend meetings

    2. (update Update 5/16): done

2019 Second Half

Possible work items for the TAC in the second half of 2019 include:

  1. Follow up to the Streamlining SP Onboarding Working Group

  2. Follow up to the Attributes for Collaboration and Federation Working Group

    1. The TAC is reviewing the draft of InCommon’s response to the above two groups through February

    2. Update 5/23: The recommendations the above two working groups made are planned or underway as part of InCommon's response.

  3. Deployment Profile Working Group

    1. Possible follow up later in 2019 after hiatus and Kantara ratification of revised SAML2int

    2. Create an R&E specific profile to layer on top of SAML2int

    3. Might factor into Baseline, badging, automated testing

  4. Development of a test InCommon federation

  5. Badging for Participants

    1. Possible sub-group with members of CTAB and TAC

  6. Address onboarding and communication gaps

    1. Reaching the right people on campus

  7. Maturity model outline for adoption of federation technologies and protocols

...