expirationWarningThreshold

[Brent Putman]

On 5/19/17 4:20 PM, Tom Scavo wrote:
> Thanks for clarifying. All of that makes sense. It needs to be
> documented, however.

I added a parenthetical qualifier to the expirationWarningThreshold
docs on the wiki. 

I don't know how one would document any of the other.  It's not about
Shibboleth software, it's about general metadata concepts.


>
>> We in fact do not actually literally expunge expired metadata, but we don't
>> return it from a metadata resolve call.
> This is not made clear in all the documentation I've read. Of course I
> could have missed something.

The not expunging part isn't.  But it's an internal implementation
detail, so I don't know why a deployer would care.  The necessity of
the entity to be valid to be used is documented in the
requireValidMetadata attribute. 


>
> That, too, is not clear by reading the documentation.

It's in the requireValidMetadata attribute.

>  I was under the
> impression that invalid metadata was ignored, full stop.

As far as the calling code is concerned, it is ignored, full stop.  
What I mentioned is the internal impl detail of the resolvers.  This is
the dev list, so I'm mentioning details of the software that would be
irrelevant to an end-user deployer.


>  Also, what is
> isRequireValidMetadata? I can't find that in the docs.

That's the Java method name, corresponds to the resolver config
attribute requireValidMetadata:

https://wiki.shibboleth.net/confluence/display/IDP30/MetadataConfiguration#MetadataConfiguration-Attributes

It's been there since v2.2.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20170519/13c6dfd1/attachment.html>