envoyproxy/envoy

specify a grace period to allow an request with expired jwt when using jwt auth filter

Open

#7,693 opened on Jul 23, 2019

View on GitHub
 (2 comments) (1 reaction) (0 assignees)C++ (5,373 forks)batch import
design proposalenhancementhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

[feature request] When using jwt auth filter we should be able to specify a grace period to allow an request with expired jwt for the specified amount of time?

Or may be provide a way to forward the requests with expired JWT to a different upstream.

Use Cases: There will be some occasions where the client will not be able to get the latest jwt token as the jwt issuer might be down or jwt token issuer might be stormed with many token issue requests at a specific time and that it can serve only some of them. for that time period when client sends a expired JWT we can allow the request to succeed. Or if this is a anti pattern we can simply allow that request to be forwarded to a different upstream cluster for handling that requests with expired jwts.

Contributor guide

Research direction
Examine the JWT auth filter source code in Envoy (source/extensions/filters/http/jwt authn/ or similar). Understand how JWT validation and expiration check is implemented. Design a configuration option for a grace period (e.g., clock skew tolerance) that allows expired tokens within that period. Consider the security implications and possible use cases like fallback upstreams.
Tech stack
cpp
Domain
backendsecurity
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++GitBasic JWT knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45