Skip to content

VLTCLT-62 Fix V4 signature using proxyPath instead of original path#463

Open
nicolas2bert wants to merge 2 commits intodevelopment/8.5from
bugfix/VLTCLT-62/signature
Open

VLTCLT-62 Fix V4 signature using proxyPath instead of original path#463
nicolas2bert wants to merge 2 commits intodevelopment/8.5from
bugfix/VLTCLT-62/signature

Conversation

@nicolas2bert
Copy link
Contributor

@nicolas2bert nicolas2bert commented Feb 16, 2026

When a VaultClient has a proxyPath set (ex: /_/backbeat/iam), _signRequest() signs the request with options.path which includes the proxyPath, instead of the original path argument (/).

Vault sets the canonical URI to / (standard IAM logic), which lead to signature mismatch error = InvalidAccessKeyId.
The bug was introduced in vaultclient 8.3.18 by commit 6fd9996 (VLTCLT-37: rely on aws signer to sign requests).

Every version from 8.3.18 onward is affected.

The old code:

passed the original path argument to the signing function.

The new code:

passes options directly to signer.sign(), where options.path has already been overwritten with the proxyPath.

The _signRequest method already receives path as its 4th parameter. it just doesn't use it.

@bert-e
Copy link
Contributor

bert-e commented Feb 16, 2026

Hello nicolas2bert,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options
name description privileged authored
/after_pull_request Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval Bypass the pull request author's approval
/bypass_build_status Bypass the build and test status
/bypass_commit_size Bypass the check on the size of the changeset TBA
/bypass_incompatible_branch Bypass the check on the source branch prefix
/bypass_jira_check Bypass the Jira issue check
/bypass_peer_approval Bypass the pull request peers' approval
/bypass_leader_approval Bypass the pull request leaders' approval
/approve Instruct Bert-E that the author has approved the pull request. ✍️
/create_pull_requests Allow the creation of integration pull requests.
/create_integration_branches Allow the creation of integration branches.
/no_octopus Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity Change review acceptance criteria from one reviewer at least to all reviewers
/wait Instruct Bert-E not to run until further notice.
Available commands
name description privileged
/help Print Bert-E's manual in the pull request.
/status Print Bert-E's current status in the pull request TBA
/clear Remove all comments from Bert-E from the history TBA
/retry Re-start a fresh build TBA
/build Re-start a fresh build TBA
/force_reset Delete integration branches & pull requests, and restart merge process from the beginning.
/reset Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

@bert-e
Copy link
Contributor

bert-e commented Feb 16, 2026

Incorrect fix version

The Fix Version/s in issue VLTCLT-62 contains:

  • None

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

  • 8.5.4

Please check the Fix Version/s of VLTCLT-62, or the target
branch of this pull request.

@bert-e
Copy link
Contributor

bert-e commented Feb 16, 2026

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

// be computed with the IAM canonical path '/' — which is what Vault
// verifies against. A mismatch causes InvalidAccessKeyId (VLTCLT-37).
describe('V4 signature with proxyPath must use IAM canonical path', () => {
const { createHmac, createHash } = require('crypto');
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should be required on top of the file

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants