Repository navigation
Conversation
This was referenced Nov 21, 2026
Enforce source-network policy for administrative bearer tokens
cloudfoundry/cloud_controller_ng#5686
Draft
This branch has not been deployed
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
Add an operator-controlled, deployment-wide source-network policy for administrative token issuance,
refresh, and use, preserving ordinary tokens and default behavior when disabled.
uaa.admin,cloud_controller.admin,cloud_controller.admin_read_only,cloud_controller.global_auditor, andzones.<id>.admin; optional exact additions extend this set.ordinary clients can still introspect administrative subject tokens.
Configuration prefix:
uaa.admin_token_network_policywithenabled,allowed_cidrs, andadditional_protected_scopes. Identity-zone/client configuration cannot weaken the deployment policy.Validation
scopes, and final enhancer overrides.
generateDocssucceeded: 126 docs tests and rendered Slate HTML.git diff --checkis clean.Draft pending security/CI review, database/grant/zone integration coverage, and real-ingress forged-header
tests. No live deployment was changed. Operators must configure actual trusted proxies and NAT/VPN
egress; documentation addresses are not defaults. External transforming proxies/custom authentication
managers must preserve equivalent checks on original credentials.
Coordinated changes
UAA alone cannot enforce use at offline JWT resource servers. Companion draft PRs:
This is a network allowlist, not cryptographic binding to the original issuance IP or a complete
delegation/escalation boundary. Other resource servers need independent enforcement.