| Warning | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
We have exciting news! An updated InCommon Federation wiki is now available. Please visit the new InCommon Federation Library for updated content. This wiki is preserved for historical records only. It will no longer be updated. We invite you to come check out the new Library. Don't forget to update your bookmarks accordingly.
|
This is the SAML home page for the InCommon Federation.
...
InCommon strongly recommends that all entities (IdPs and SPs) support SAML V2.0 Web Browser SSO. The benefits of SAML V2.0 are significant, to both individual participants and the Federation as a whole; see What's New in SAML 2? for more information.
Currently there are a few dozen IdPs in the InCommon Federation that do not support SAML V2.0. Consequently, SPs can not safely ignore legacy SAML V1.1 protocols, which tends to favor the latter over SAML V2.0. As a community, we are caught in a chicken-and-egg situation that can be traced back to those legacy IdPs. If most of those IdPs were to add SAML V2.0 to their portfolio, the dynamics would immediately change, for the benefit of all Federation participants.
...
For their part, SPs are encouraged to support SAML V2.0 as well. An SP's migration path to SAML V2.0 is actually more complicated than that of the IdP, but if done correctly, an SP can make a smooth transition to SAML V2.0 with little or no disruption to services.
Local Resources
- Benefits of SAML V2.0What's New in SAML 2?
- IdP Support for SAML V2.0
- SP Support for SAML V2.0
- SAML V2.0 Frequently Asked QuestionsInCommon SAML V2
- Software Guidelines for SAML V2.0 Profiles
- InCommon Use of SAML V1.1 and V2.0: A Statistical Summary (last updated 2012-05-29)
...
- Wikipedia resources:
- OASIS SAML Technical Committee
| Attachments | ||
|---|---|---|
|