feat: add route-to-scope map with report-only rollout mode - #6
Merged
Conversation
Split the Docker publish into per-platform build jobs (amd64 on ubuntu-latest, arm64 on a native arm runner) that push by digest, then a merge job that assembles the multi-arch manifest. Adds metadata-action based tagging, pinned action SHAs, and per-ref concurrency. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Adds a static YAML route map (ROUTES_FILE) that enforces OAuth2 scope requirements per method and path, evaluated against the X-Forwarded-Method/X-Forwarded-Uri headers Traefik sends: - segment-glob path patterns (* = one segment, trailing ** = remainder) with first-match-wins evaluation and a configurable default decision - scope implication following the EDC grammar <api>:[<resource>:]<action>, with admin > write > read and api-level/ wildcard scopes covering resource-level requirements - ENFORCE_ROUTES=false (default) runs report-only: violations are logged but only the legacy ?scope= check decides, enabling a safe rollout before flipping enforcement on Legacy verbatim ?scope= checks are unchanged and documented as deprecated in the README. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
wolf4ood
approved these changes
Jul 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ROUTES_FILE) enforcing OAuth2 scope requirements per HTTP method and path, evaluated against theX-Forwarded-Method/X-Forwarded-Uriheaders Traefik sends (seeroutes.example.yaml)*= one segment, trailing**= any remainder), first match wins, with a configurabledefault: allow|denyanyOfscope requirements are satisfied via scope implication following the EDC grammar<api>:[<resource>:]<action>:admin ⊇ write ⊇ read, and api-level/wildcard scopes cover resource-level requirementsENFORCE_ROUTES=false(default) runs report-only: route-map violations are logged but only the legacy?scope=check decides — allowing a safe rollout before flipping enforcement on?scope=checks are unchanged and documented as deprecated🤖 Generated with Claude Code