InCommon metadata support

[Jeffrey Eaton <>]

What I do for testing is set up an IDP otherwise identical to my production 
server, and in /etc/hosts on my desktop to point at the test server IDP 
directly.  This lets me test config changes out in a fairly “real” way 
without affecting the campus at large.

-jeaton


> On Mar 1, 2016, at 6:05 PM, Wessel, Keith 
> <>
>  wrote:
> 
> Hi, Tom and others,
> 
> Apologies if this has already been answered. I didn't see any thoughts on 
> it elsewhere, though.
> 
> I finally configured our test IDP to pull InCommon and eduGAIN metadata 
> from the MDQ server instead of the full aggregate. I'd like to test this 
> out and leave it in place for a while on our test IDP. Problem is this: 
> obviously, none of the SPs that the MDQ server knows about will know about 
> our test IDP: it's not the IDP our campus has published in InCommon. And 
> since there's no command-line tool in the IDP at this point that one can 
> use to display metadata on a given entity from the IDP's metadata resolver, 
> there's not much I can do with my new setup at all. Clearly, I'm not going 
> to point my production IDP cluster at a service for metadata when that 
> service is considered beta.
> 
> Any thoughts on how an IDP operator can kick the tires on the MDQ server 
> and be an active participant in the pilot?
> 
> Keith
>