Feature #10333
closedrgw: support AWS4 authentication
0%
Updated by Yehuda Sadeh over 9 years ago
- Subject changed from rgw: support AWS4 to rgw: support AWS4 authentication
Updated by Javier M. Mellid almost 9 years ago
I started this feature and I have some initial bits working now but I don't have the right permissions to ask for assignation or update the "Assignee" field in tracker.
Would it be possible taking care of this feature implementation? If so, anybody updating the 'Assignee' field to jmunhoz? Thanks!
Updated by Yehuda Sadeh almost 9 years ago
- Assignee set to Javier M. Mellid
Done. You should be able to modify these fields under the rgw project now.
Updated by Javier M. Mellid almost 9 years ago
I've just created a pull request to merge a first version for supporting Amazon's S3 signature V4 (from now on, AWS4).
The patch implements the basic required primitives to work with AWS4 (sha256 crypto, encoding, and so on), and is able to authenticate HTTP requests that don't include the parameters in the query string (only as HTTP headers) and that do not contain a body. This is work in progress, and I hope to submit a new pull request for this part as soon as possible.
The patch is fully mergeable, so if done it will partially support V4. As said before, I am working on bringing the remaining features.
Note that V2 authentication continues to work as usual.
Any feedback is welcomed.
Pull request is available at:
Updated by Josh Durgin almost 9 years ago
- Status changed from New to Fix Under Review
Updated by Javier M. Mellid almost 9 years ago
Pull request updated with the missing bits. It contains the whole feature.
Updated by Sage Weil about 8 years ago
- Status changed from Fix Under Review to Resolved