different AuthnContextClassRef for different discovered IDP

[Peter Schober]

* Cantor, Scott <cantor.2 at osu.edu> [2016-06-08 14:57]:
> > peter.schober at univie.ac.at> wrote:
> >
> >I'm just saying I don't see where/how you'd add such configuration
> >details (3-tuples of: entityID-contentsetting-value or 2-tuples of
> >entityID-authContextClassRef) to the Shibboleth SP.
> 
> No. Per-IdP behavior is limited to what can be pulled from
> RelyingParty settings (the SP's version of that). There is an issue
> filed that relates to this use case, though it's not phrased that
> way. I don't know if it will make the release this month or not,
> depends on time.

You're referring to SSPCPP-608?  I now see that for the OP it would
probably be easiest to add the relevant content setting into an
RelyingParty element, and have one RelyingParty element for each IDP.
Not sure that's doable or what the tradeoffs are.
-peter