Metadata validity interval of 24 minutes?

[Daniel Smedegaard Buus]

On Mon, Oct 12, 2015 at 11:09 AM, Ian Young <ian at iay.org.uk> wrote:
>
>> On 12 Oct 2015, at 09:01, Daniel Smedegaard Buus <danielbuus at gmail.com> wrote:
>>
>> Error filtering metadata from
>> https://browsertest.localhost/login/sso/metadata.xml
>> org.opensaml.saml2.metadata.provider.FilterException: Metadata's
>> validity interval, 237588141ms, is larger than is allowed, 86400000ms.
>>
>> So now the allowed interval is 24 minutes?
>
> As Rod says, this is the result of your configuration, not a default in the code.
>
> You have configured the maximum allowed validity interval to be one day (86400000ms = 86400s = 24*3600 seconds = 24 hours).
>
> The validUntil of the metadata being analysed is more than one day in the future (237588141ms = 237588s = 66 hours = 2.75 days).
>

LOL :D You're right! What retarded calculus I performed there :'D

> Specifying that the validity interval for metadata is only a day is an extremely aggressive setting. For comparison, most large federations use values in the range of a few days to several weeks. It's ultimately up to you, though, to choose values that make sense.

Roger that!

FTR, it turned out that the issue of all this was actually the virtual
machine not properly synchronizing the time from the host OS. I was
looking at the log and seeing timestamps that perfectly matched those
in OS X, so I assumed the time was properly synced. However, running
date reveals that, yes, the clock matches, but in the VM it's still
Friday :D

Forced an ntp update, and it's behaving just fine now. Sorry :) And
thanks again!

Daniel