Date: Fri, 29 Mar 2024 12:52:42 +0000 (UTC) Message-ID: <1003816361.7971.1711716762293@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_7970_946116203.1711716762290" ------=_Part_7970_946116203.1711716762290 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Working Group Chair: Walter Hoehn, University of Memphi= s
Working Group Flywheel: Nick Roy, Internet2
Email List: fed-interop-wg@incommon.org . T= o subscribe this list, email sympa@incommon.org with the subject line subscr= ibe fed-interop-wg
The implementation profile this group cr= eated in the fall/spring has been transitioned to the Kantara Federation In= teroperability Working Group.
The new home for this work on Github can= be found here:
h=
ttps://github.com/KantaraInitiative/SAMLprofiles/tree/master/edit/fedintero=
p
A rendered version of the profile can be= found here:
https://kantar= ainitiative.github.io/SAMLprofiles/fedinterop.html
We encourage all who are interested to participate in, or at least = monitor the ongoing push toward publishing the profile as a Kantara recomme= ndation. Information about the Kantara FI-WG can be found at: https://kantarainitiative.org/groups/federation-interoperability-work-grou= p/
The group has delivered its final report to the InCommon TAC, available = here:
Final Report - Federation Interoperability Working Group 1=
A PDF of the SAML Implementation Profile generated by the work of this g= roup is available here:
SAML V2.0 Implementation Profile for Federation Interoperability 2= 0160418.pdf
Access to the repository that contains the asciidoc source for the spec = is documented here: Accessing GitLab Repository
The group has concluded the comment period, with no comments external to= the group's membership. Finalization of the document and report to t= he TAC will be prepared shortly.
U= pdate: January 26, 2016:
The group has concluded drafting of the interoperability profile:
http://walterhoehn.com/dl/SAML-Impl-Profile/rend= ered/main.html
This has been shared on the InCommon Participants, Shibboleth Developers= , and REFEDS lists, for a public comment period lasting through Feb= ruary 15, 2016. Comments are welcomed at: fed-interop-wg@inc= ommon.org.
The working group is well on its way to having a draft ready for public = review. Although not fully "feature complete," and still undergoing h= eavy revision, much of the "SAML v2.0 Implementation Profile for Federation= Interoperability" is in place, and can be seen here:
http://walterhoehn.com/dl/SAML-Impl-Profile/rend= ered/main.html
This document is updated every 5 minutes from changes pushed to its sour= ce control repository by group members, so it's always current.
If you're interested, please take some time to examine the document and = provide feedback either by joining and commenting on the mailing list (see = subscription info above) or by contacting the flywheel, Nick Roy, at nroy (= at) internet2 dot edu.
When InCommon was created 10+ years ago, it was an explicit goal to keep= the bar for membership and operational participation as low as possible. T= his helped to grow the Federation to its current size. However, this has al= so hindered interoperation. Members cannot make any real assumptions about = policy, practices, and the supported functionality at other member sites wh= en attempting to interoperate. Both IDPs and SPs suffer from this problem. = Areas that are affected include:
This Working Group is charged with developing both minimal and best prac= tice statements in order to improve the "interoperate by default" situation= .
Different audiences can impact different aspects of this problem:
This Working Group will need to develop lists for all three audiences.= p>
The Federation Interoperability Working Group will:
This Working Group is charged with developing the "WHAT" of interoperati= on in several different areas. Follow on efforts will be charged with devel= oping specific technical recommendations for "HOW" sites can accomplish the= WHAT.
This group is encouraged to think in terms of "levels" of compliance in = each area (e.g. baseline, better, best).
This group is encouraged to coordinate, as appropriate, with other Feder= ations and via REFEDS.
The group might want to have separate subgroups working on implementatio= n vs deploy requirements.
Note: The InCommon Priorities item also mentions developing a replacemen= t for the POP. The TAC has asked the AAC to approve and begin work on = the TrustMark WG Charter that they developed, and to send the resulting rep= ort back to the TAC. The TAC will then develop a cover memo and assemble a = package of documents to complete the Steering 2015 item.
Membership in the Working Group is open to all interested parties. Membe= rs join the Working Group by subscribing to the mailing list, participating= in the phone calls, and otherwise actively engaging in the work of the gro= up.
Details for accessing the working group's version control repository are here.