spaces.at.internet2.edu has been upgraded to Confluence 6.12.2. If you have any questions and/or concerns, please contact us at collaboration-support@internet2.edu
Page tree
Skip to end of metadata
Go to start of metadata

InCommon TAC Minutes - March 30, 2017

AIs from past calls

(AI) TAC members are asked to review the document regarding TIER and potential changes to Shibboleth and see if there is anything that should be added.

(AI) TAC members are asked to review and comment on the wiki page documenting the proposed new policy for IdP endpoint locations.

(AI) Tom Scavo will develop documentation related to SP endpoint locations and expects to have that ready for the March 30 TAC meeting. [NA]

Minutes - March 30, 2017

TAC Members Attending:  Mark Scheible, Jim Jokl, Janemarie Duh, Tom Mitchell, Kim Milford, Tom Barton, Chris Misra, Walter Hoehn, Mike Grady, Steve Carmody,, Albert Wu

Others Attending: Nick Roy, David Walker, Dean Woodbeck, Ian Young, IJ Kim, Tom Scavo, Kevin (had to jump off at 20min after the hour), Ann

Action Items from this call

(AI) Nick Roy will put the Federation Manager development roadmap on the wiki

(AI) Mark Scheible will communicate to the AAC about using/promoting the technical-discuss list

(AI) Kim Milford will promote the technical-discuss list among the REN-ISAC community

(AI) TAC members should review the charter and membership process prior to Global Summit

(AI) Albert Wu will make edits to the OIDC working group report, as suggested on today’s call.

(AI) Mark Scheible and Ann West will develop an executive summary of the report and recommendations for the InCommon Steering Committee.

(AI) Steve Carmody will draft a proposal (maybe a working group charter) for a way to facilitate conversations and track the progress of campuses using OIDC.

(AI) Janemarie Duh will draft a charter for a proposed Service Provider Onboarding Working Group

(AI) Mark Scheible and Ann West will discuss whether a working group is needed for the attribute release work plan item and, if so, make a proposal to Steering.

(AI) Mark will develop a google doc or sheet with each work plan item, some recommendations, and providing the ability to +1 or to volunteer for charter development (if working group is needed) 

Unresolved AIs from past calls

(AI) TAC members are asked to review the document regarding TIER and potential changes to Shibboleth and see if there is anything that should be added.

(AI) TAC members are asked to review and comment on the wiki page documenting the proposed new policy for IdP endpoint locations.

Ops Update

Domains in Endpoint Locations - nothing new since last week

  • Need to update internal procedures for the RA (Tom S)

  • Need to set a date/deadline (Tom S)


Incident Response - Tom Scavo gave an update on the March 10 incident in which eduGAIN changed the order of entities in their metadata, which caused issues with the InCommon aggregate. Tom Scavo and Ian Young are working on solutions that would insulate InCommon from such changes in the future 


InCommon Metadata Aggregate v7 - Ian has developed this new version and InCommon is evaluating this release internally. Tom Scavo has provided a list of issues addressed.


Trust and Identity Updates

  • There was a development team and business stakeholder meeting in Ann Arbor this week concerning the roadmap for Federation Manager enhancements. (AI) Nick Roy will put the roadmap on the wiki in the not-too-distant future

  • Internet2 went live with a ticketing system (ServiceNow). The first step was moving the admin@incommon.org email list to ServiceNow. Participants still send email to admin@, but responses and follow-up will come via ServiceNow.


Technical-Discuss Email list

This email list is in place and being used
. (AI) Mark Scheible will communicate to the AAC about using/promoting this list
. (AI) Kim Milford will promote the list to the REN-ISAC community
.

Global Summit Meeting Agenda

  • TAC will meet Monday, April 24 (8:30-10 am)

  • Agenda items

    • review of TAC charter and membership process (AI) TAC members review charter and membership process
    • Process for developing 2018 work plan


OIDC Survey Working Group - Final Report and Recommendations

Albert Wu proposed that TAC accept the working group’s report and recommendations
. The report has some urgency concerning the recommendations related to APIs and mobile devices. There is less urgency about the second recommendation (developing OIDC/OAuth federation standards). It was suggested that this difference be made more clear in the report.


TAC Accepts OIDC Working Group Report

TAC accepted the working group report, with Albert making edits based on today’s discussion (there were no objections to accepting the report and subsequent edits.

(AI) Mark Scheible and Ann West will develop an executive summary of the report and recommendations for the InCommon Steering Committee.

Community Webinar on 2017 Work Plan

Janemarie reviewed the feedback on the 2017 Work Plan received during the community webinar (36 attended).

The  “SP onboarding” item received good support. This will likely become a working group, with the charter being specific about the scope. This item also overlaps with the attribute release item.

Discovery 2.0 did not have a lot of support, but most webinar attendees were IdPs, whereas this is a problem mainly for service provider operators

2017 Work Plan

Things to consider about each item:

  • Are there items that are not just InCommon, and so need broader discussion?

  • Is REFEDS or another group already working on the problem?

  • Should we create an InCommon Working Group for the item?


Next Steps with OIDC

  • Pass along the working group recommendation about including OIDC in the TIER products to TIER Ad Hoc Advisory (so do not create a working group).

  • There are campuses that have OIDC in production or are working on doing so. (AI) Steve Carmody will draft a proposal (maybe a working group charter) for a way to facilitate conversations and track the progress

  • The larger task about incorporating OIDC with federations is of international scope, so no working group created.


Improving Community Access/Visibility

  • This item does not require a working group, but is something we need to keep in front of ourselves and continue the wiki development (public information).

Service Provider Onboarding

  • (AI) Janemarie Duh will draft a charter for a proposed working group

Federation Interoperability

  • 
This item is being addressed in the Deployment Profile Working Group and will be rechartered to continue its work

Attribute Release

InCommon Steering is developing some work in this area, specifically around R&S. 


(AI) Mark and Ann will discuss whether a working group is needed here (and, if so, propose that to Steering). 


(AI) Mark will develop a google doc or sheet with each work plan item, some recommendations, and providing the ability to +1 or to volunteer for charter development (if working group is needed)

Next Meeting - Thursday, April 13 - 1 pm ET


 

  • No labels