envoyproxy/gateway

feat: method based authz should support paths to allow fine grained authz.

Open

#5,605 opened on Mar 25, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (802 forks)auto 404
area/apihelp wantedtriage

Repository metrics

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

Description

Description:

Method based authz should support paths to allow fine grained authz.

Example:

Distinction between /example/foo (read:foo) and /example/bar (create:bar) in the SP. BUT: Both routes are part of one HTTPRoute with spec.rules.matches[x].path: /example.

[optional Relevant Links:]

HTTP headers and method authz

Contributor guide

Research direction
Examine the existing method based authorization implementation in Envoy Gateway (e.g., from PR #5393) and extend it to support path based matching. Understand how HTTPRoute rules are processed and how authorization policies are applied, then add path matching logic.
Tech stack
go
Domain
backendsecurity
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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
KubernetesGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50