Per-Entity Metadata Working Group

[Chris Phillips <>]

From my perspective, I would NOT drop the others for the simple reason
that if we want vendors to support this, we should highlight that they(the
technology builders) are missing this feature.

For instance, ADFS is almost present everywhere Shibboleth is or people
are installing it at a higher frequency than Shib just to get to
Office365/Azure. 

If ADFS actually actually had better SAML2 support (support for
aggregates, easier attribute mapping and now soon to be a need to support
MDQ, that would be a big plus to all our communities globally.

You can substitute ADFS with Ellucian, Ping, and/or WSO2 and then tack on
18+ months from when things are fully baked of course :)

Sure is a bit more work, but when those players (of which we are expending
energy on at least 3 of them now) come to this topic - and you know they
will have to, it becomes an exercise to fill in gaps as opposed to do
discovery on what the gaps which in itself is a large task..


C

  

On 2016-08-16, 3:56 PM, "Nick Roy" 
<
 on
behalf of 
>
 wrote:

>Hello,
>
>John Bradley says that Ping support for MDQ is not production-ready, and
>looped me in with David Chase to elaborate.  I have not heard back from
>David.  I also have not heard anything further from Zion Brewer, beyond
>that he was seeking out input from some engineering teams and hadn't
>heard back from them.  Maybe we should just annotate the information we
>have about non-Shibboleth/SSP implementations as guesswork, or delete
>those rows from our analysis entirely?
>
>Nick
>