metadata early warning system

[Cantor, Scott]

On 4/5/18, 10:13 AM, "dev on behalf of Tom Scavo" <dev-bounces at shibboleth.net on behalf of trscavo at gmail.com> wrote:

> 1) Modify the behavior of boolean attribute
> MetadataProvider/@requireValidMetadata: If @creationInstant exists and
> is in the future, the metadata is not valid

That would not be appropriate since the definition of valid metadata doesn't involve that attribute. We also don't change the meaning of existing settings, pretty much ever. Which would mean yet more settings, which I'm opposed to.

> 2) Add attribute MetadataProvider/@freshnessInterval (to complement
> @expirationWarningThreshold, which is misnamed [1])

I think more settings is a bad direction.

I'm also much more concerned about the limitations I've identified in the dynamic plugins to worry about aggregates. Until those issues are dealt with, there shouldn't be more time spent on the old way of doing things.

-- Scott