Difference in clocks between client and server cause problems about node-opcua

[EirikVea]

@erossignon Looks good! Now it warns of the time discrepancy and continue working as expected.

[AndreasHeine]

https://reference.opcfoundation.org/Core/Part4/v104/docs/5.5.2

Clients should request a new SecurityToken after 75 % of its lifetime has elapsed. This should ensure that Clients will receive the new SecurityToken before the old one actually expires.

and

Clients should accept Messages secured by an expired SecurityToken for up to 25 % of the token lifetime. This should ensure that Messages sent by the Server before the token expired are not rejected because of network delays.

in opc ua utc is used!
did you use NTP time sync?

[erossignon]

https://reference.opcfoundation.org/Core/Part4/v104/docs/5.5.2

Also interesting article:

https://reference.opcfoundation.org/Core/Part6/v105/docs/6.3

A server that cannot connect to the NTP time sync could interact with the Discovery server to update its time and correct time drift. I haven't seen this implemented

[erossignon]

Should be fixed in [email protected] , please confirm