envoyproxy/envoy

Allow filtering of headers sent in CheckRequest to gRPC ext authz

Open

#21,535 opened on Jun 1, 2022

View on GitHub
 (2 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/ext_authzarea/grpcenhancementhelp wanted

Repository metrics

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

Description

Title: Allow filtering of headers sent in CheckRequest to gRPC ext authz

Description:

The HTTP ext authz allows for the filtering of headers from the request sent to the ext authz service (allowed_headers: https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/http/ext_authz/v3/ext_authz.proto#extensions-filters-http-ext-authz-v3-authorizationrequest), but the gRPC version does not.

In my case a lot of non-required headers are being passed along to my ext authz, I would prefer if they were not. I could of course move to straight HTTP but I don't really want to do that either.

Contributor guide

Research direction
Implement header filtering for gRPC ext authz by following the pattern used in HTTP ext authz, specifically modifying the CheckRequest to filter headers before sending.
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++Envoy development environment
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40