Peter,<br><br>I totally agree with you. I was just trying to test some error cases and see how IdP handles these cases, and seems like it is very reasonable. We cannot do everything just best effort.<br><br>By the way, I have submitted the issue in the bug system.<br>
<br clear="all"><div>Yaowen</div>
<br><br><div class="gmail_quote">On Wed, Mar 20, 2013 at 1:18 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">
* Yaowen Tu <<a href="mailto:yaowen.tu@gmail.com">yaowen.tu@gmail.com</a>> [2013-03-20 02:51]:<br>
<div class="im">> Log says the metadata file has not changed since last refresh.<br>
><br>
> While I am expecting to see an error log says the file doesn't<br>
> exist.<br>
<br>
</div>If that's the case you should report an issue in the bug tracker.<br>
<br>
Note that in many year of production we never "lost" local files (in<br>
your case metadata) and there are plenty of things you can do to<br>
protect yourself against such cases (e.g. cfengine or tripwire could<br>
make sure the correct file exists in the correct place with the<br>
correct content).<br>
If "missing" local files are generally an issue you'd be in much more<br>
trouble if any of the files in conf/ or the keystore in credentials/<br>
were gone -- how would you expect the software to protect you from<br>
that?<br>
<br>
If the issue is defining metadata providers which point to<br>
non-existing files, well, you've got a broken configuration. I'd make<br>
sure such a config never goes live on a production server (e.g. by<br>
having a test instance in place and actually test stuff there).<br>
<br>
Its much more likely for remote metadata resources (outside your<br>
control) to become unavailable, at least temporarily, which you cannot<br>
influence with local tooling. The IdP handles these cases fine (with<br>
a plethora of settings you've seen for the metadata provider, to<br>
influence behaviour).<br>
<span class="HOEnZb"><font color="#888888">-peter<br>
</font></span><div class="HOEnZb"><div class="h5">--<br>
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.net</a><br>
</div></div></blockquote></div><br>