authenticateMessage() giving "Stale timestamp" error. #86

Closed
mikeal opened this Issue Jul 12, 2013 · 1 comment

Comments

Projects
None yet
2 participants
Contributor

mikeal commented Jul 12, 2013

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.

Owner

hueniverse commented Jul 12, 2013

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment