Date: Thu, 28 Mar 2024 21:00:48 +0000 (UTC) Message-ID: <944334856.7007.1711659648911@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_7006_2045231378.1711659648910" ------=_Part_7006_2045231378.1711659648910 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The InCommon Technical Advisory Committee (TAC) supports InCommon= =E2=80=99s mission =E2=80=9Cto create and support a common framework for tr= ustworthy shared management of access to online resources.=E2=80=9D It is a= n advisory body to the InCommon Steering Committee. It provides advice on I= nCommon=E2=80=99s operational processes and practices, strategies, capabili= ties, and roadmap to InCommon Steering and to InCommon Operations (OPS).&nb= sp;The TAC meets biweekly throughout the year. Members serve three-y= ear terms.
Charter - The InCommon TAC charter is available on the InCommon website.
Visit the = span>InCommon Community Leadership pag= e for the c= urrent list of members.
There is also a page listing all curr= ent and past members.
Access Entity Category + SAML= 2Int Deployment - SAML Subject Identifier Adoption Strategy
Federation Testing Working Gr= oup
A list of curren= t and recently concluded InCommon Working Groups (including TAC Ch= artered) is available on the wiki.
Public TAC Minutes (posted within two weeks of the meeting)
Materials for TAC = Members (private)
Technical Discussion List
Follow discussions about technical is= sues or current trends or ask technical questions related to InCommon and g= lobal federation.
List: technical-discuss@incommon.=
org To subscribe, send email =
to
** Note, this list does not replace specific product support lists, = so questions on specific products should continue to be posted to those lis= ts (e.g. Shibboleth, Grouper, etc.).