Skip to content

Conversation

@rohityadavcloud
Copy link
Member

Params need to be dropped as apikey & secretkey based URL has all the params and it causes signature validation issues when the same params are also posted again. For example, add host API with username, password params.

Params need to be dropped as apikey & secretkey based URL has all the
params and it causes signature validation issues when the same params
are also posted again. For example, add host API with username, password
params.

Signed-off-by: Rohit Yadav <[email protected]>
@rohityadavcloud
Copy link
Member Author

Steps to reproduce the issue:

  • Create profile with only apikey and secret key set
  • Try to add a host, it fails with HTTP 401, on deep dive - it appears signature fails to match

Fix: don't send both encoded params as part of the URL and also param that may be posted.

Copy link
Contributor

@shwstppr shwstppr left a comment

Choose a reason for hiding this comment

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

Code LGTM. Signature is added only for API key and secret key based profiles

@rohityadavcloud rohityadavcloud merged commit 1f45761 into main May 20, 2024
@rohityadavcloud rohityadavcloud deleted the signature-bugfix branch May 20, 2024 10:20
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.

2 participants