authenticateMessage() giving "Stale timestamp" error.

[mikeal]

apparently this is only an issue with authenticateMessage() as the http client will adjust the clock for you. I need a similar way to do this with authenticateMessage.

[hueniverse]

When establishing the connection, have the server send a timestamp message using hawk.crypto.timestampMessage(). Then in the browser call hawk.client.authenticateTimestamp() which will update the internal clock offset. Check that authenticateTimestamp() returns true (it will not update the clock if false).

Lemme know if this works for you and I'll publish 1.1.0.

[lock]

This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.