Date: Fri, 29 Mar 2024 01:18:17 +0000 (UTC)
Message-ID: <362452353.7353.1711675097224@ip-10-10-7-29.ec2.internal>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_7352_860146396.1711675097223"
------=_Part_7352_860146396.1711675097223
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Attending
Members=
- Chris Phillips, CANARIE (chair) &nbs=
p;
- Marina Adomeit, GEANT <=
/li>
- Warren Anderson, University of Wisco=
nsin-Milwaukee /LIGO
- Tom Barton, U. Chicago <=
/span>
- Jill Gemmill, Clemson =
span>
- Karen Herrington, Virginia Tech &nbs=
p;
- Todd Higgins, Franklin & Marshal=
l College
- Tom Jordan, U Wisc - Madison &=
nbsp;
- Christos Kanellopoulos, GEANT =
- Les LaCroix, Carleton College =
Guests<=
/p>
- Janemarie Duh, Lafayette College
- Keith Wessel, University of Ill=
inois at Urbana-Champaign
- Albert Wu, Internet2
Internet2
- Kevin Morooney =
li>
- Ann West
- Steve Zoppi
- Emily Eisbruch =
li>
Regrets=
- Rob Carter, Duke
- Nathan Dors, U Washington
- Nick Roy, Internet2
DISCUSSION
FIM4R gap assessment final document: ht=
tp://doi.org/10.26869/TI.112.1
- Thanks for all the contributions.
- KarenH is w=
orking at VA Tech on Advance Research Computing Task Force doing stra=
tegic planning and she may share the FIM4R recommendations doc.=
Tour of InCommon TAC 2019 plans (=
Discussion/feedback - led by Janemarie Duh, Keith Wessel, InCommon TA=
C Co-chairs)
- IDP as a Service Working Gro=
up
This Working Group will be kickin=
g off soon
Strawman charter was crafted by T=
om Barton
Goal is to reach long tail of res=
earch and scholarship
challenge of getting researchers =
access to services
Eric Goodman wrote a background d=
oc on SAML proxies,
Likely the WG will look at a SAML=
front end
Mary McKee from Duke is involved =
as the InCommon TAC sponsor for the IDP as a Service WG
When call for participation goes =
out for the IDP as a Service working group, it will be important to recruit=
from all stakeholder groups, including vendors
Some commercial partners ha=
ve expressed interest in participating.
-
- Q: Who would be the target group for=
a potential hosted service?
- A: Hope that campuses could subscrib=
e to this service, want to make it easy for them to hook up to a service, m=
ore than a SAML IDP, but also a service that follows (meets standards for) =
InCommon Collaboration ready approach
-
- Q: Is IDP as a service going to driv=
e requirements for TIER software?
- A: IDP as a service will be built with ITAP (InCommon Trusted Access &n=
bsp;Platform) in mind.
<=
/p>
- Perhaps IDP as a service can help ca=
mpuses running a non InCommon friendly infrastructure. S=
o there may need to be more connectors. Connectors may or may not be called=
proxies. There will likely be multi tenant structures.
- There are vendors interested in offe=
ring a service to fill the IDP as a Service need and this could=
impact whether or not InCommon needs to stand up a service.
- if commercial provider stands up the infrastructure, then do we incorpo=
rate their connector into InCommon Trusted Access Platform? eTo be decided in the future
- Suggestion to have someone from EDUC=
AUSE working on IDP as a Service working group. It was noted that the=
InCommon community will have a need for IDP as a service.
- It was noted that there can be secur=
ity concerns with IDP as a service
Q: is TAC keeping in mind the FIM4R response as they plan for 2019=
?
A: yes, TAC will review that document again http://doi.=
org/10.26869/TI.112.1
Federation 2.0 Working Group
-
- This is another new InCommon TAC (an=
d REFEDs) working group
- planned to last about one year
- Judith Bush (OCLC) <=
/span>and Tom Barton are cochairs=
-
- This group =
has started calls
-
- Janemarie will provide CACTI members=
access to the background document
- It was noted that eventually the con=
nection of services issue should be discussed in REFEDs
- SP Proxy will likely be part of the =
solution moving forward.
- Sometimes SPs federate but it does n=
ot work in the SAML environment.
- Will fit into the solutions being en=
visioned by the working groups.
Q: is the solution for proxies part of IDP as a service? Or =
Federation 2.0
- A: Janemarie: could be part of both
- There is also chance to have a follo=
w-on to TAC Streamlining WG and Attributes for collaboration WG that finish=
ed in 2018.
Setting Priorities&n=
bsp;
- Kevin noted that Internet2 managemen=
t may need to make decisions based on the input from the Advisory boards su=
ch as CACTI and TAC. The FIM4R response has been extremely helpful fo=
r management making prioritization decisions. It=E2=80=99s about managing e=
xpectations around what we will do and won=E2=80=99t do and the pace=
- It was noted that vendors are offeri=
ng supporting products. InCommon could potentially certify (in some way) th=
ose that meet the desired standards. IdP as a service may come first.=
Proxy could be at a later point.
- Concerning the best way for CACTI , =
CTAB and InCommon TAC to work together, it has been proposed to have&=
nbsp;representatives at each others calls.
- Perhaps another follow-up call for the chairs would be helpful.&n=
bsp;
- CTAB is working on a Baseline=
Expectations roadmap and CTAB wants to share that with the other adv=
isory groups for input and feedback.
Janemarie thanks CACTI for the good q=
uestions and discussion.
Rest of the agenda saved for future call
=
Communications opportunities on=
T&I roadmap planning (Discussion - 10 min - various)
Engaging 2019 planning with CTAB and TIER Architects
2019 TechEx session (Suggested by TAC)
Share final paper with TAC, CTAB, Component Architects, FIM4R group=
span>
Feedback on Results of Kevin sharing this with TI PAG, Steering, Big =
Ten Academic Alliance IAM group
Areas already engaged, others places to make inroads to?
=
li>
Messages to take to FIM4Rv2 meeting at TIIME in Vienna next we=
ek (Chris, TomB, Nick will attend)
CACTI review staff write-up from Albert/TomB
Open call to other TI governance groups for a roadmapping sess=
ion
Closing out the MACE-Dir transi=
tion work
Need a volunteer to:
Get list of authors as complete as possible - work with Keith =
Hazelton and David Bantz
Work with Keith Hazelton to resolve any remaining comments
Work with librarian to get the sunset plannin=
g doc published in the TI document repository
Follow up with REFEDS on the following items to ensure progres=
s is being made, report back to CACTI:
New mailing list
Schema editorial board governance
Transfer of assets (see sunset planning doc for full list)
Namespaces / registries (URN/OID)
Chris' work on Les' URN recommendations - status check<=
/p>
Schema (edu*)
Other web content - MACE-Dir wiki, mace=
dir.org
additional future topics:
Proposal to focus OIDC-Deployment working group on a deployment gu=
ide for the Shibboleth OIDC extension (Nathan )
Next CACTI Call : Tues Feb 19=
, 2019
=
------=_Part_7352_860146396.1711675097223--