Require explicit flag for gateway auth enforcement#468
Merged
Conversation
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
1 participant
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
GATEWAY_AUTH_REQUIRED=1is set.Why
The #467 deploy still failed beta integration with 403s: a gateway auth secret exists in staging, but
GATEWAY_AUTH_REQUIREDis not set and the generated integration client does not send a bearer token. This makes the enforcement switch explicit so deployment can proceed without accidentally breaking the current public gateway behavior.Testing
env -u UV_FROZEN uv run pytest tests/gateway/test_auth.py tests/gateway/test_endpoints.py -qenv -u UV_FROZEN uv run pytest -qenv -u UV_FROZEN uv run --with ruff ruff format --check src