Date parsing issue?

[Phil Pishioneri]

On 2019/2/8 10:16 AM, Brian Biggs wrote:
> We have a password nearing expiration intercept flow configured, which
> has been working fine for a couple of months.
>
> Last night, for only 1 hour (between 6pm and 7pm PST), our IDP
> generated the following error:
>
> 2019-02-07 18:00:02,409 - 130.157.xxx.xxx - INFO
> [net.shibboleth.idp.profile.logic.DateAttributePredicate:164] -
> 2019-03-10T02:00:02Z is not a valid date for the configured date parser


If that timestamp had been in your local time zone, it would be invalid
due to the Daylight Saving Time change on March 10 (no 02:mm hour that
morning). But to me the 'Z' should put it outside that hour. (Maybe
there's a missing time zone offset in the output?)

The time frame you mentioned (6pm-7pm PST) with an 8 hour offset from
UTC would map to 0200-0300 UTC.

-Phil