Metadata validity interval and fun with timezones

[Cantor, Scott]

On 10/31/13, 11:28 AM, "Wessel, Keith" <kwessel at illinois.edu> wrote:
>
>Our IDPs all started complaining about the metadata validUntil time being
>too far in the future this week. Our local metadata has a 7-day validUnti
>time, and the validityInterval in relying-party.xml is set to 7 days.
>Starting at exactly 2 AM on Sunday morning, it started complaining about
>the validity interval being between 45 and 60 minutes too long; we update
>local metadata every 15 mins.

What version are you on? I think I fixed that in 2.4.

>The time interval and the 2 AM Sunday thing seem to scream timezone data
>problem. Problem is we're on a recent Java release - 6.0U45. And it has
>the 2012i tzdata in it. I even updated our tzdata to the latest available
>from Oracle 2013g. 2013h came out last week. Oracle doesn't have an
>updater for it yet, but I'm doubtful that'll help.

No, if it's what I'm thinking it's due to a weird bug in the way we were
computing durations. We weren't using a fixed baseline that doesn't cross
DST so it was giving us different results.

-- Scott