<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 30, 2015 at 7:11 AM, Peter Schober <span dir="ltr"><<a href="mailto:peter.schober@univie.ac.at" target="_blank">peter.schober@univie.ac.at</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">* Tom Scavo <<a href="mailto:trscavo@gmail.com">trscavo@gmail.com</a>> [2015-03-30 14:44]:<br>
<span class="">> > I don't use InCommon for on-campus systems, and I don't supply the<br>
> metadata for our IdP to them with it. I host the metadata file, but<br>
> I also sign it every morning, and it expires every few days, and the<br>
> (Shibboleth) SPs check all of that when they load it every few<br>
> hours.<br>
><br>
> Hopefully, soon, you (and others) won't have to do that any more:<br>
><br>
> <a href="http://mdq-beta.incommon.org/global/entities/urn%3Amace%3Aincommon%3Aosu.edu" target="_blank">http://mdq-beta.incommon.org/global/entities/urn%3Amace%3Aincommon%3Aosu.edu</a><br>
<br>
</span>You'd still have to point them elsewhere and explain to them why they<br>
should trust any output from that, same as with an aggregate that gets<br>
filtered after downloading (whether it's your own or a federation's).<br></blockquote><div><br></div><div>It's not that hard to get them to point elsewhere especially when they don't get a choice in the matter. </div><div><br></div><div>Dave</div><div><br></div></div>-- <br><div class="gmail_signature">David Langenberg<div>Identity & Access Management</div><div>The University of Chicago</div></div>
</div></div>