Support setting leeway for token expiration validation
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 124
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
It seems the current echo-jwt middleware does not support the WithLeeway option from golang-jwt, which leads to strict token expiration checks without allowance for clock skew.
Adding support for configuring leeway would help tolerate minor time differences during token validation.
Thanks!
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by locating the echo-jwt middleware's token validation path and reviewing how it configures golang-jwt validation. Trace how parser or validation options are passed, then confirm that a configurable leeway can tolerate minor clock skew during expiration checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100