is this error storage related ?

[Cantor, Scott]

> I’m tracking down a newly introduced issue that has appeared locally since
> moving to 3.2.1 and hazelcast storage. I’m just looking to vet my thoughts
> that this is due to the storage mechanics and not some errant setting WRT the
> sessions in general.

I'm not really sure, I don't know how you could end up with that error. I'd probably need to cross check the actual data that's stored.

> It looks to me like this is trying to up date the idp session with the latest time-
> stamp info and the times are not different enough to allow this so the
> exception is thrown..

No, the error is in deserializing the AuthenticationResult stored in the session's records. The last used time field is computed using a fairy ugly calculation but it's based on the expiration of the record in the storage. It even has a failure mode so that if there isn't one, it defaults it based on the authentication time.

So, I don't know how the code could ever end up with a value of zero, which is why the Constraint is there.

I don't see how that one specific error could result from a storage plugin, but OTOH nobody's said anything like this is happening...

Maybe there's some kid of retrieval failure that's not being picked up earlier, but...I dunno, it has to parse JSON before it ever would reach that stage.

-- Scott