New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rgw: aws4: handle UNSIGNED-PAYLOAD under header auth #8601

Merged
merged 1 commit into from Apr 17, 2016

Conversation

Projects
None yet
4 participants
@jmunhoz
Copy link
Contributor

jmunhoz commented Apr 14, 2016

Fixes: http://tracker.ceph.com/issues/15499

Signed-off-by: Javier M. Mellid jmunhoz@igalia.com

rgw: aws4: handle UNSIGNED-PAYLOAD under header auth
Fixes: http://tracker.ceph.com/issues/15499

Signed-off-by: Javier M. Mellid <jmunhoz@igalia.com>

@liewegas liewegas added this to the jewel milestone Apr 14, 2016

@jmunhoz

This comment has been minimized.

Copy link
Contributor

jmunhoz commented Apr 14, 2016

In the jargon of AWS S3, this patch adds the missing bits to handle the 'Unsigned payload option' in 'Transfer Payload in a Single Chunk' (Authorization Header way)

s3-tests has not coverage for the combo (PUT + UNSIGNED-PAYLOAD + Authorization Header) cause our test cases use boto2 with the 'Signed payload option' mainly. Testing with libcloud requires changing the host/region to speak to RGW and using the verify_hash=False parameter in 'driver.upload_object' method.

One RGW S3 provider in libcloud is almost finished but I am running some testing before asking to go upstream in libcloud for the next days.

@mattbenjamin mattbenjamin self-assigned this Apr 14, 2016

@yehudasa

This comment has been minimized.

Copy link
Member

yehudasa commented Apr 15, 2016

lgtm

@liewegas liewegas merged commit 0859625 into ceph:master Apr 17, 2016

2 checks passed

Signed-off-by all commits in this PR are signed
Details
default Build finished.
Details

@jmunhoz jmunhoz referenced this pull request May 19, 2016

Closed

Add S3_RGW storage driver #786

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