Closed myeung18 closed 2 years ago
Hi @myeung18. Thanks for creating this issue.
I was able to reproduce this bug. It looks like we were not limiting the headers used for request-signing in Secretless to those used to sign the original request. I have a pull request up to fix this, over at https://github.com/cyberark/secretless-broker/pull/1432. I've tested it locally and confirmed that the fix works.
Once it is reviewed by the team and merged it should make its way into the next release. Please do create a build from the branch and evaluate it, it would help to get sign off from your side that the changes fix the issue.
Summary
I am trying secretless broker at my local to access aws s3 buckets, I can list the buckets fine, but I can’t create any new bucket. is this a bug?
I tried aws cli w/o secretless broker in between to create bucket, and it works fine. I am using the same account as above, and it is an admin.
Steps to Reproduce
Steps to reproduce the behavior:
Expected Results
should be able to perform whatever the account is able to do with the returned connection.
Actual Results (including error logs, if applicable)
The aws connection created/returned from secretless broker should be no difference to the connection created without the secretless broker.
Additional Information
Add any other context about the problem here.