Metadata validity interval and fun with timezones

[Wessel, Keith]

Unfortunately, you're right. With the value set to 604800, I still get the same thing.

10:44:44.511 - ERROR [edu.internet2.middleware.shibboleth.common.config.BaseService:188] [session=] - Configuration was not loaded for shibboleth.RelyingPartyConfigurationManager service, error creating components.  The root cause of this error was: org.opensaml.saml2.metadata.provider.FilterException: Metadata's validity interval, 607516512ms, is larger than is allowed, 604800000ms.

I've just pushed the validity times out a bit. A little padding doesn't really hurt. But I am curious if anyone has any other theories.

Keith

-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Thursday, October 31, 2013 10:40 AM
To: Shib Users
Subject: Re: Metadata validity interval and fun with timezones

On 10/31/13, 11:37 AM, "Wessel, Keith" <kwessel at illinois.edu> wrote:

>Thanks, Scott. Yes, we are on 2.4. I'll try changing to the millisecond
>values.

Then I don't think that's the bug, so I don't expect it will fix it.

-- Scott


--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net