Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

JWT: 'Expiration time' claim ('exp') is too far in the future

See original GitHub issue

Bug Report

Current Behavior This error began when I upgraded to v9 from v7

When running probot run index.js I get the following error:

ERROR probot: 'Expiration time' claim ('exp') is too far in the future

I am not creating any tokens manually, this just occurs when the bot tries to authenticate in order to make the first request.

Expected behavior/code Authentication with the GitHub API on probot@^9 should create valid API tokens

Environment

Probot version(s): 9.2.13
Node/npm version: Node v10.16.0
OS: OSX 10.14.5

Possible Solution

Issue Analytics

State:
Created 4 years ago
Comments:24 (11 by maintainers)

Top GitHub Comments

4reactions

warrenbuckleycommented, Jun 12, 2019

Hmm sounds like a game of spot the difference is in order then @gr2m

It’s not quite the same though

 exp: Math.floor(Date.now() / 1000) + 60,  // JWT expiration time

Current

const now = Math.floor(Date.now() / 1000);
exp: now + 60 * 10, // JWT expiration time (10 minute maximum)

So previous one just added on 60 seconds from current issued time and the current one adds on 10 minutes from current time.

4reactions

issue-label-bot[bot]commented, Jun 11, 2019

Issue-Label Bot is automatically applying the label bug 🐞 to this issue, with a confidence of 0.91. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.