IdPv3 and Hathitrust: how to resolve and release SAML

Peter Schober peter.schober at univie.ac.at
Mon Jul 10 14:08:15 EDT 2017


* Cantor, Scott <cantor.2 at osu.edu> [2017-07-10 19:37]:
> I'm just trying to highlight "don't support it" as a choice as much
> as I can.

It may be the existence of the latter case (see below) that prompts
some IDPs to deploy with less suitable starting values.

Or it's the federation operators' fault aiming to maximize the interop
between SPs and IDPs, pushing IDPs to support something that many SPs
couldn't care less about.  And all with the best of intentions. (What
do they say about The Road To hell? ;))

> Whether it makes sense for an SP to ever simply say "I won't accept
> a non-targeted value" is a very interesting question worth
> exploring.

At least within Europe I can imagine this being a function of trying
to minimize their legal risk (or maximize their compliance) at a given
day and legislation when `rand() mod 2` evaluates to 1, signifying
that persistent NameIDs now do [not] constitute PPII.
-peter


More information about the users mailing list