lp:~redbo/swift/swauthdelim

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:~hudson-openstack/swift/trunk at revision 176

gholt (community): Approve on 2011-01-18

Chuck Thier (community): Approve on 2011-01-17

Diff: 161 lines (+31/-32)

5 files modified

doc/source/deployment_guide.rst (+1/-1)
doc/source/howto_installmultinode.rst (+2/-2)
etc/proxy-server.conf-sample (+4/-4)
swift/common/middleware/swauth.py (+15/-16)
test/unit/common/middleware/test_swauth.py (+9/-9)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Bug #703487: make swauth config use something other than '::' to denote a private url

Undecided

Fix Released

Link a bug report

Related blueprints

174. By Mike Barton on 2011-01-17

modify default_swift_cluster option format

173. By Mike Barton on 2011-01-14

Execute object server fsyncs in a thread pool so they don't hold up the workers.

172. By Chuck Thier on 2011-01-14

Add docstrings and pointers in the docs for swift3

171. By Mike Barton on 2011-01-14

Support more query args and headers in the swift3 middleware

170. By Mike Barton on 2011-01-14

hopefully last of the i18n gettext calls

169. By anticw on 2011-01-14

Small fixes to make audit work robustly in the case where people liked to put funny chars in their container and object names.

168. By Mike Barton on 2011-01-14

use python-netifaces to get local IP addresses.
I'll add that to the package depends right after this is merged.

167. By Mike Barton on 2011-01-14

pep8 fixes for swift3 middleware

166. By gholt on 2011-01-14

Fix for GETing a manifest that has an empty listing

165. By FUJITA Tomonori on 2011-01-14

Seems that the following operations work with boto:

- List of buckets
- Create bucket
- Delete bucket
- List of objects in a bucket
- PUT object
- GET object
- DELETE object
- HEAD object

Swift account (something like AUTH_89308df71f274e33af17779606f08fa0) is used as AWSAccessKeyId.
Swift password (passed to swift-auth-add-user) is used as AWS Secret Access Key.

S3 client concatenates selected elements of a request to form a string, uses AWS Secret Access Key to calculate the HMAC of that string, and then put the HMAC value to the HTTPAuthorization header.

The proxy server sends the account info, the formed string of a request, and the HMAC value included with the request to the auth server. The auth server finds AWS Secret Access Key from the account info, use the key to calculate the HMAC of the string, and sees if it matches the HMAC value.