envoyproxy/gateway

Support of allowed_client_headers_on_success in extAuth http SecurityPolicy

Open

#3,787 opened on Jul 8, 2024

View on GitHub
 (5 comments) (8 reactions) (0 assignees)Go (802 forks)auto 404
help wanted

Repository metrics

Stars
 (2,871 stars)
PR merge metrics
 (PR metrics pending)

Description

We need to set a cookie in our ext auth service, for this we need allowed_client_headers_on_success

Currently we use EnvoyPatchPolicy to add the configuration, but native support would be great

Thank you

Contributor guide

Research direction
Examine the ExtAuthz filter's code in the api/v1alpha1 package to understand how other header related fields are implemented, then add a new field for allowed client headers on success and wire it through the translation layer to the Envoy xDS configuration.
Tech stack
go
Domain
backendapi
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.
Half day
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
GoKubernetes
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65