Fix vault gateway auth propagation#21865
Merged
prashantkumar1982 merged 2 commits intodevelopfrom Apr 3, 2026
Merged
Conversation
Contributor
|
I see you updated files related to
|
Contributor
|
✅ No conflicts with other open PRs targeting |
18fde74 to
57c9a35
Compare
|
jmank88
approved these changes
Apr 3, 2026
justinkaseman
approved these changes
Apr 3, 2026
5c334a2 to
4279bb8
Compare
|
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
orgIDandworkflowOwneronto all authenticated gateway vault requestsexpectedLabelsin vault label-validation errorsRoot Cause
The vault capability's gateway handler was forwarding capability requests without overwriting identity fields from the trusted auth result, so the vault capability was seeing empty fields. Separately, allowlist propagation could lag long enough for gateway and node authorization to disagree, and validator errors did not show which labels were compared.