Date: Fri, 29 Mar 2024 07:14:48 +0000 (UTC) Message-ID: <1758026384.7601.1711696488873@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_7600_691521961.1711696488871" ------=_Part_7600_691521961.1711696488871 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Attending: Mark Scheible, Matt Brookover, Janemarie Duh= , Judith Bush, Mike Grady, Eric Goodman, Tom Demeranville, Kim Milford
Regrets: Keith Wessel, Eric Kool-Brown
With: Nick Roy, IJ Kim, Dave Shafer, David Walker, Shan= non Roddy
Updated TAC Charter - Mark sent the updated charter to = Sean Reynolds, chair of InCommon Steering, and asked to have it on Steering= =E2=80=99s next agenda for approval (Steering next meets Monday, June 4).= p>
Status of MACE-Dir / next steps with REFEDS - MACE-Dir = work will move to REFEDS, since this is a global activity. At the Global Su= mmit meeting, MACE-Dir members thanked Keith Hazelton for leading this for = so many years.
Baseline Expectations - Release of the Federation Manag= er Tuesday, May 29, will strongly recommend metadata changes conform with B= aseline. CTAB and the project team are working on communications leading up= to the PA change (June 15) and beyond.
eduGAIN Steering Meeting - Voting members approved an e= duGAIN SAML policy change requiring federations to do specific things with = their metadata. Entities need a technical and support contact. There will c= ome a time when eduGAIN will drop a federation if they submit metadata with= out those. When that happens, if there are InCommon organizations that do n= ot have those contacts, we will stop exporting those entities to eduGAIN.= p>
eduGAIN also recommends submitting metadata with a 4096-bit key. This is= planned as part of our MDQ rollout. Also, eduGAIN has a =E2=80=9Cshould=E2= =80=9D to adding mdrpi:RegistrationInfo to every InCommon entity descriptor= s. We do not do this.
Federation Manager - Released some bug fixes this week = and will have more next week when we do the Baseline Expectations update.= p>
MDQ Implementation - As part of automating metadata sig= ning, we need a Hardware Security Module. We are having trouble with gettin= g the Shibboleth MDA to work with the Amazon HSM via PKCS#11, so we are wor= king to develop a signing bean for the MDA that will work with the HSM via = Java API supplied by Amazon.
Streamlining SP Onboarding - reviewing feedback from co= mmunity consultation. Suggesting a late June wrap-up.
Attributes for Federation - Consultation ends June 4, t= hen the working group will meet to discuss the community input.
OIDC Deployment - Met recently. Coordinating discussion= s to take place at TNC. Discussing architectural deployment profiles.
Deployment Profile - Just met. Comment period has ended= and the WG has discussed those at the last two meetings. Looking at the en= d of June as being finished with that. Also talking about a community call = to discuss the comments.
Janemarie, Heather, and Judith have been holding discussions via email. = Judith has agreed to serve as one of the co-chairs. The group needs to look= strategically at where interfederation needs to go. The hope is to recruit= a co-chair and spin this group up in June.
This has simmered for many years. Service Providers in science projects,= for instance, continue to have problems with IdPs providing attributes and= accurate attributes. InCommon is seeing more problems with participants en= tering metadata using IdP software that doesn=E2=80=99t work in the federat= ion. Are there ways we can encourage people to participate and pay attentio= n to email and email lists. Here are some excerpts from a TAC email thread.=
Possible solutions?