Repository navigation
Conversation
Multiple required credentials on one route currently require every token. Select one entry per group from the original headers while preserving independent credential requirements.
Exercise selection, rejection before upstream contact, credential rotation, and an in-flight request through the real proxy. Fuzz header values and audit output for ambiguous selection and secret leaks.
rohangpta
marked this pull request as ready for review
October 21, 2026 20:11
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.
Two workers may need to call the same API using different accounts while holding only proxy tokens. Today, two matching
require: trueentries each require their own token, so neither credential can be used independently.Add
selection_groupfor alternative, required header credentials. A request must select exactly one matching entry. Missing, unknown, or ambiguous tokens and conflicting header writers are rejected before fetching secrets. Ungrouped entries keep their existing behavior.Maintainers - let me know if you would like additional clarity re use-cases or examples; I'd be happy to share more information.