'Issued at' claim ('iat') must be an Integer representing the time that the assertion was issued
See original GitHub issueBug Report
Current Behavior When running the Probot app locally, I get the following error on startup:
ERROR probot: 'Issued at' claim ('iat') must be an Integer representing the time that the assertion was issued
Expected behavior/code No errors should occur on startup.
Environment
- Probot version(s): 9.2.19
- Node/npm version: v10.16.0
- OS: OSX 10.14.5
Possible Solution
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (9 by maintainers)
Top Results From Across the Web
SonarQube PR Decoration failing iat time error
... HTTP code (was 401): {“message”:"'Issued at' claim ('iat') must be an Integer representing the time that the assertion was issued" ...
Read more >IAT claim not getting inserted in the JWT Token - Stack Overflow
The token given by our Identity Server is not having the "iat" claim. After authenticating the user from our side, we need to...
Read more >jenkinsci/github-branch-source-plugin - Gitter
GHFileNotFoundException: https://api.github.com/app {"message":"'Issued at' claim ('iat') must be an Integer representing the time that the assertion was ...
Read more >RFC 7519: JSON Web Token (JWT) - » RFC Editor
JSON Web Token (JWT) Overview JWTs represent a set of claims as a JSON object ... "iat" (Issued At) Claim The "iat" (issued...
Read more >SonarQube Pull Request Decoration - Linux Dev Space
... HTTP code (was 401): {“message”:”'Issued at' claim ('iat') must be an Integer representing the time that the assertion was issued” ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Anyone else seeing this error from GitHub’s API, check the clock of your system - the timestamp must not be in the future. In our case the machine’s clock drifted one minute forward.
Yeah let’s do that. I’ll keep an eye out on though. Thanks for your help!