rich7420 opened a new pull request, #12010:
URL: https://github.com/apache/ozone/pull/12010

   ## What changes were proposed in this pull request?
   
   Signed aws-chunked uploads (`STREAMING-AWS4-HMAC-SHA256-PAYLOAD` and its 
`-TRAILER` variant) are only verified in secure mode, where OM returns the 
derived signing key, but the existing S3 SDK integration tests run against a 
non-secure cluster.
   
   This adds a Kerberos-secured MiniOzoneCluster test that uploads through S3 
Gateway with the AWS SDK v2 client. Valid PutObject and UploadPart requests, 
with and without a CRC32C trailer, must succeed. For the rejected cases, the 
test changes one part of the body after signing (a data chunk, the final chunk 
signature, or the signed trailer) or signs a wrong checksum. It expects 
`SignatureDoesNotMatch` or `BadDigest`, and checks that the existing object or 
part is left unchanged. The test runs with and without Ratis datastream, 
because S3 Gateway attaches the validator on a separate path for each.
   
   ECDSA (SigV4a) is not covered: S3 Gateway accepts only `AWS4-HMAC-SHA256` 
authorization, so there is no ECDSA verification to test.
   
   ## What is the link to the Apache JIRA
   
   https://issues.apache.org/jira/browse/HDDS-15143
   
   ## How was this patch tested?
   
   New `TestS3SignedChunksInSecureCluster` and 
`TestS3SignedChunksInSecureClusterWithRatisStreaming`; the signature cases fail 
when S3 Gateway does not attach the chunk validator.
   CI: https://github.com/rich7420/ozone/actions/runs/42874171889
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to