docs: clarify proxy cache trust boundary for upstream token-service discovery#706
Open
1seal wants to merge 1 commit intogoharbor:mainfrom
Open
docs: clarify proxy cache trust boundary for upstream token-service discovery#7061seal wants to merge 1 commit intogoharbor:mainfrom
1seal wants to merge 1 commit intogoharbor:mainfrom
Conversation
…iscovery document that proxy cache follows upstream WWW-Authenticate bearer realm challenges when obtaining tokens. clarify that token service endpoints can differ from the registry host, and recommend trusted endpoints plus least-privilege upstream credentials. docs-only change; no behavior or config changes.
Vad1mo
approved these changes
Feb 19, 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
4 participants
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.
docs: clarify proxy cache trust boundary for upstream token-service discovery
what this changes
this PR adds documentation notes in two places:
docs/administration/configure-proxy-cache/_index.mddocs/administration/configuring-replication/create-replication-endpoints.mdthe notes clarify that:
WWW-Authenticateauthentication challenges to obtain tokenswhy
this makes the existing trust model explicit for operators using proxy cache, without changing Harbor behavior or adding new configuration.
compatibility
validation
related context
this PR follows maintainer guidance to submit this clarification in
goharbor/website.