Versions Compared

Old Version 14

changes.mady.by.user trscavo@internet2.edu

Saved on

compared with

New Version Current

changes.mady.by.user Nicole Roy

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Working Group Agenda/Notes

Note

These notes are live-scribed at: https://docs.google.com/document/d/1KuCp_q_oJfeFlA37XNsK4eB7zKdlWTAt42reHS2scDw/edit?usp=sharingNotes for this Working Group were live-scribed here

Working Group Chair: Walter Hoehn, University of Memphis

Working Group Flywheel: Nick Roy, Internet2

Email List:  fed-interop-wg@incommon.org . To subscribe this list, email sympa@incommon.org with the subject line subscribe fed-interop-wg

Update: June 6, 2016:

The implementation profile this group created in the fall/spring has been transitioned to the Kantara Federation Interoperability Working Group. 

The new home for this work on Github can be found here: 

https://github.com/KantaraInitiative/SAMLprofiles/tree/master/edit/fedinterop
 

A rendered version of the profile can be found here: 

https://kantarainitiative.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 recommendation. Information about the Kantara FI-WG can be found at: https://kantarainitiative.org/groups/federation-interoperability-work-group/

Update: March 3, 2016:

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 group is available here:

SAML V2.0 Implementation Profile for Federation Interoperability 20160418.pdf

Access to the repository that contains the asciidoc source for the spec is documented here: Accessing GitLab Repository

Update: February 17, 2016:

The group has concluded the comment period, with no comments external to the group's membership.  Finalization of the document and report to the TAC will be prepared shortly.

Update: January 26, 2016:

The group has concluded drafting of the interoperability profile:

http://walterhoehn.com/dl/SAML-Impl-Profile/rendered/main.html

This has been shared on the InCommon Participants, Shibboleth Developers, and REFEDS lists, for a public comment period lasting through February 15, 2016.  Comments are welcomed at: fed-interop-wg@incommon.org.

Update: October 29, 2015:

The working group is well on its way to having a draft ready for public review.  Although not fully "feature complete," and still undergoing heavy 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/rendered/main.html

This document is updated every 5 minutes from changes pushed to its source 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.

Problem Statement

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. This helped to grow the Federation to its current size. However, this has also hindered interoperation. Members cannot make any real assumptions about policy, practices, and the supported functionality at other member sites when attempting to interoperate. Both IDPs and SPs suffer from this problem. Areas that are affected include:

...

  1. Sept 2015
    1. An initial list of baseline requirements that a SAML software implementation must meet
    2. An initial list of baseline requirements that deployers of SAML software must meet
  2. Dec 2015 
    1. A complete, fully specified set of baseline requirements that a SAML software implementation must meet
    2. A complete, fully specified set of baseline requirements that deployers of SAML software must meet
    3. A List of which items can be "tested"
  3. ??
    1. A list of "better" requirements that a SAML software implementation must meet
    2. A list of "better" requirements that deployers of SAML software must meet.
    3. Make the encryption certificate in SP metadata optional
    4. Test IdPs for metadata refresh and tag the ones that don't with hide-from-discovery

Related Resources

  1. The saml2int Deployment Profile.
  2. A list of proposed Changes to saml2int.
  3. A Draft IdP Deployment Checklist.
  4. A Draft InCommon SAML Implementation Profile
  5. Kantara eGovernment Implementation Profile
  6. Net+ Guidance for Services
  7. CIC Cloud Services Cookbook
  8. Kantara Federation Interoperability Working Group - Disposition of Comments on SAML v2.0 Implementation Profile for Federation Interoperability
  9. Good Federation Citizenship - IAM Online
  10. The Federation Lab SAML Test Suite (git)
  11. OASIS SAML2 Wiki 
  12. Scott's list of OASIS specifications (see below)

...


See Also

InCommon Working Groups Home