envoyproxy/envoy

Oauth2 filter: Support private_key_jwt in addition to token_secret

Closed

#40,127 opened on Jul 8, 2025

View on GitHubContributor guide
 (6 comments) (0 reactions) (1 assignee)C++ (5,373 forks)batch import
area/oauthenhancementhelp wanted

Repository metrics

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

Description

Title: Oauth2 filter: Support private_key_jwt in addition to token_secret

Description: Some IdPs encourage/enforce use of private_key_jwt in favor of client secret for client authentication per recommendation in RFC9700. Oauth2 filter does not support this yet.

Relevant Links

Contributor guide

Research direction
Review the existing OAuth2 filter implementation in Envoy, particularly the client authentication handling using token secret. Understand the private key jwt flow per RFC 9700 and authlete documentation. Identify where to add support in the filter configuration and validation. Check if there are any related discussions or PRs linked in the issue comments.
Tech stack
cpp
Domain
securityauthentication
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++OAuth2Envoy filter architecture
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20