We encounted a Heuft OPC server that didn’t send a timestamp in the OpenSecureChannelResponse message.
Yet it did send the correct timestamp in all other responses, so by adding a few more checks and also updating the offset on session creation fixes the problem.
And at the same time it can help to prevent new clock skew in cases where the channel is kept alive very long and new sessions are created within the existing channel.
We encounted a Heuft OPC server that didn’t send a timestamp in the
OpenSecureChannelResponse
message.Yet it did send the correct timestamp in all other responses, so by adding a few more checks and also updating the offset on session creation fixes the problem.
And at the same time it can help to prevent new clock skew in cases where the channel is kept alive very long and new sessions are created within the existing channel.