Missing support for STREAMING-AWS4-HMAC-SHA256-PAYLOAD on certain endpoints #239

New issue

Closed

opened 2022-02-10 14:51:56 +00:00 by lx · 1 comment

lx commented

2022-02-10 14:51:56 +00:00

Owner

Here on CreateBucket: https://gist.github.com/eitch/3c4e2fa8c7c6d52f87b3792ad1219299

TODO list:

check all of the different endpoints where STREAMING-AWS4-HMAC-SHA256-PAYLOAD can be used (possibly it can actually be used on all endpoints that have a non-empty body?)
make a generic mechanism to handle such payloads

Here on CreateBucket: https://gist.github.com/eitch/3c4e2fa8c7c6d52f87b3792ad1219299 TODO list: - [ ] check all of the different endpoints where STREAMING-AWS4-HMAC-SHA256-PAYLOAD can be used (possibly it can actually be used on all endpoints that have a non-empty body?) - [ ] make a generic mechanism to handle such payloads

lx added the

scope

s3-api

label 2022-02-10 14:51:56 +00:00

quentin commented

2022-02-10 14:55:11 +00:00

Owner

The PR that implements it on Minio: https://github.com/minio/minio/pull/2370

They say:

// Verify if the request has AWS Streaming Signature Version '4'. This is only valid for 'PUT' operation.

Also, we should add STREAMING-AWS4-HMAC-SHA256-PAYLOAD to our S3 compatibility list, in the features section!

The PR that implements it on Minio: https://github.com/minio/minio/pull/2370 They say: ``` // Verify if the request has AWS Streaming Signature Version '4'. This is only valid for 'PUT' operation. ``` Also, we should add `STREAMING-AWS4-HMAC-SHA256-PAYLOAD` to our S3 compatibility list, in the features section!