Skip to content

[docs] auth: auth: document cli-proxy-egress relay for DIFC credential isolation under network-isolation #7387

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lpcox merged 2 commits into from
Aug 15, 2026
Merged

[docs] auth: auth: document cli-proxy-egress relay for DIFC credential isolation under network-isolation #7387

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
58eac8c
docs: document cli-proxy-egress relay for DIFC credential isolation u…
github-actions[bot] Aug 15, 2026
1a1d9fc
Potential fix for pull request finding
lpcox Aug 15, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/awf-config-spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -655,6 +655,15 @@ When `security.difcProxy.host` is set, `GITHUB_TOKEN` and `GH_TOKEN` MUST
be excluded from the agent environment. These tokens SHALL be held
exclusively by the external DIFC proxy.

Under `--network-isolation`, the credential-bearing cli-proxy sidecar remains on
`awf-net` only. When `security.difcProxy.host` is classified as external
(`host.docker.internal`, an IP address outside `awf-net`'s subnet, or a dotted DNS name), AWF creates a separate,
credential-free `cli-proxy-egress` relay that is the only CLI-proxy component
dual-homed onto the external bridge; it forwards solely to the configured DIFC
host and port and never receives `GITHUB_TOKEN` or `GH_TOKEN`. When the DIFC
proxy is an attached sibling container already reachable on `awf-net`, no relay
is created.

## 10. Effective Token Budget Enforcement

*This section is normative.*
Expand Down
Loading