release-21.2: server: CancelSession propagates gateway metadata #75832
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.
Backport 1/1 commits from #75814.
/cc @cockroachdb/release
Fixes #75758.
Previously, HTTP session cancelation requests from the DB Console were
routed to the proper node without passing along the gateway metadata
necessary for authentication. This enabled users without the
CANCELQUERY
option to cancel the sessions of other users, which theyshould not have had permission to do.
This commit addresses that issue by properly propagating that gateway
metadata in the CancelSession endpoint.
Release note (bug fix): The CancelSession endpoint now correctly
propagates gateway metadata when forwarding requests.
Release justification: Category 3: Fixes for high-priority or high-severity bugs in existing functionality