InCommon metadata support

[Tom Scavo <>]

On Wed, Mar 2, 2016 at 1:11 PM, Wessel, Keith 
<>
 wrote:
>
> And Tom, given it's a beta, would you call this a good or bad idea

Well, all else equal, I wouldn't do anything until my IdP were
completely migrated to Shib3. At that point, I would reconsider my
options.

> assuming I'm using the production aggregate as a fallback?

I hope you'll let me correct your terminology so there's no confusion.
The fallback aggregate on md.incommon.org is one thing (you can read
about it here: https://spaces.internet2.edu/x/-oGeBQ) but using a
chaining MetadataProvider that falls back on an aggregate if query
fails is another thing altogether. Moreover, the latter is
experimental in the sense we don't anticipate that will be the
ultimate method of per-entity metadata refresh. In fact, this is one
of the things we hope to learn by the end of this pilot.

FYI, here's our working document on MDQ server configuration:
https://spaces.internet2.edu/x/VQApBQ

Tom

> -----Original Message-----
> From: 
> 
>  
> [mailto:]
>  On Behalf Of Cantor, Scott
> Sent: Wednesday, March 02, 2016 12:08 PM
> To: 
> 
> Subject: RE: [Metadata-Support] How to test the per-entity metadata server 
> from an IDP
>
>> What I didn't realize was that folks were using this beta MDQ server in 
>> their
>> production IDPs with the InCommon production aggregate as a fallback
>> aggregate. I'll need to float that past a few folks around here, but that
>> certainly seems like a good way to participate in the pilot. So, I think 
>> that's
>> the answer I was looking for.
>
> I wasn't saying anybody was, I'm saying that's about the only practical 
> real world test of it that's not all-in.
>
> That is what the shibboleth.net SPs are doing, though, and those are 
> production (but not production in the "I'll get fired if it's down 
> occasionally" sense, so I wasn't counting them).
>
> -- Scott
>