On test environment we need to change system date to test the application.
This breaks the communication between Octopus server and the tentacle on that machine:
MessageSecurityException: The security timestamp is invalid because its creation time (‘2014-03-21T11:25:22.363Z’) is in the future. Current time is ‘2013-10-01T01:47:51.525Z’ and allowed clock skew is ‘00:05:00’.
Is there a way to ignore this mismatch, so that I can deploy to the machine that has time-travelled?
Is this running Octopus 1.6? If so it’s not possible; messages are timestamped and signed; without the clocks being relatively in sync there’s no guarantee against a replay attack or someone using an expired certificate.
Octopus 2.0 might work however, I haven’t tried it.