Date parsing issue?

[Brian Biggs]

Hi,

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

I tracked it back to the intercept flow.

The relevant config is:

<bean
   id="shibboleth.expiring-password.Condition"
   class="net.shibboleth.idp.profile.logic.DateAttributePredicate"
   c:attribute="passwordExpiration"
   c:formatString="yyyy'-'MM'-'dd'T'HH':'mm':'ss'Z'"
   p:resultIfMissing="false" p:offset="-P10D" />

Am I missing something here or does the date in the error match the 
formatString in the config bean? Is the formatString wrong?

Could this be due to switching from OracleJDK to OpenJDK?

Any insight here would be appreciated.

Thanks,
-Brian