Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Challenge timestamp and expiration is saved in database as localtime but incorrectly marked as GMT in challenge lists #1586
What did you try to do?
Trigger challenge for token and then use /token/challenges/ to list challenges for the token. Initial timestamp for challenge trigger was Mon, 22 Apr 2019 14:01:54 CDT
What outcome did you expect?
A list of challenges for the token with a timestamp of Mon, 22 Apr 2019 14:01:54 CDT and with an expiration date 120 seconds in the future. I also would've accepted a timestamp of Mon, 22 Apr 2019 19:01:54 GMT
What outcome did you experience?
A challenge with a timestamp Mon, 22 Apr 2019 14:01:54 GMT and expiration of Mon, 22 Apr 2019 14:03:54 GMT. This was incorrectly 5 hours in the past. I was able to have the correct functionality by changing the local timezone of the server from CDT to UTC.