Metadata Changeover Questions

[Peter Schober]

* Cantor, Scott <cantor.2 at osu.edu> [2015-07-22 16:16]:
> You should consider a minimal change to the metadata in InCommon
> that adds a SAML 2 ArtifactResolutionService endpoint only, no SSO
> service. That will cause the 2.0 protocolSupportEnumeration constant
> to be added to the metadata but won't change any SP behavior. That
> allows push testing of SAML 2 responses from your IdP to the SPs one
> by one to verify attribute consumption.

I assumed the OP already had SAML2 support in metadata and was merely
considering removing SAML1 wholesale. Seems that's not the case (no
sign of SAML2 for JMU, in 2015), so I misunderstood the much wider
implications of that question than removing potentially unneeded SAML1
endpoints.

For the InC community: If there still are SPs that default to SAML1
(even when both their SP and the IDPs announce SAML2 support) I'd
appreciate any attempts to put some pressure on such SPs to change to
SAML2.0.

>From my experience most of the problematic SAML1-only or
defaulting-to-SAML1 SPs fall into the academic publishers
category. Some of those are able to change the settings per
tenant/customer/IDP if approached.
But maybe use of such SPs is bigger in the UK (and Europe and Japan)
than in the US?
-peter