expiry time is not calculated correctly for access tokens
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- authentication, security
Research direction
Start by locating the access-token expiry calculation and inspect how exp is compared with JavaScript Date values. Verify expiresIn, expiresAt, and expired using exp in seconds rather than milliseconds. Done means those three values are calculated correctly for access tokens.
Written by the indexing model from the issue text.
Description
The values such as expiresIn (and expiresAt) as well as the expired boolean are not being calculated correctly
The exp should be provided in seconds, though the date comparison is using the java date in milliseconds (not divided by 1000)
- Dominant language
- TypeScript
- Stars
- 19
- Forks
- 1
- Avg merge
- 1m
- Merged PRs (30d)
- 8
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from edgefirst-dev/jwt
-
Difficulty 2/5 Half a day Newbie friendliness 45/100
edgefirst-dev/jwt#9 · 1 comment ·
All issues in edgefirst-dev/jwt
Similar issues
-
Browser Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
getsentry/sentry-javascript#24577 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agilepathway/label-checker#640 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
agentic-workflows
Difficulty 1/5 Under an hour Newbie friendliness 85/100
githubnext/rig#534 ·
-
automation missing-model model-sync provider:pioneer
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
anomalyco/models.dev#7701 ·