envoyproxy/envoy

Do we have any plans to support OIDC?

Open

#21,982 opened on Jul 1, 2022

View on GitHubContributor guide
 (8 comments) (5 reactions) (0 assignees)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: Do we have any plans to support OIDC?

Description:

OAuth2 config is tedious, if support oidc, we only need config the discover api to implement the all oauth2 feature

[optional Relevant Links:]

Contributor guide

Research direction
Research existing OIDC implementations in Envoy's codebase and understand the current OAuth2 filter architecture. Consider implementing an OIDC filter that uses the discovery URL to configure OAuth2 flows.
Tech stack
cpp
Domain
securityauthenticationauthorizationapibackend
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.
3-5 days
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++EnvoyOAuth2OIDC
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20