From 7e392b70e9a7c5f326714f313c24e780ca5efd27 Mon Sep 17 00:00:00 2001 From: FUJITA Tomonori Date: Wed, 19 Jan 2011 08:41:11 +0900 Subject: [PATCH] s3api: update the comment for the id scheme change --- swift/common/middleware/swift3.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/swift/common/middleware/swift3.py b/swift/common/middleware/swift3.py index f6a5126693..f01c510dad 100644 --- a/swift/common/middleware/swift3.py +++ b/swift/common/middleware/swift3.py @@ -32,8 +32,8 @@ To add this middleware to your configuration, add the swift3 middleware in front of the auth middleware, and before any other middleware that look at swift requests (like rate limiting). -To set up your client, the access key will be the account string that -should look like AUTH_d305e9dbedbc47df8b25ab46f3152f81, and the +To set up your client, the access key will be the concatenation of the +account and user strings that should look like test:tester, and the secret access key is the account password. The host should also point to the swift storage hostname. It also will have to use the old style calling format, and not the hostname based container format. @@ -42,7 +42,7 @@ An example client using the python boto library might look like the following for an SAIO setup:: connection = boto.s3.Connection( - aws_access_key_id='AUTH_d305e9dbedbc47df8b25ab46f3152f81', + aws_access_key_id='test:tester', aws_secret_access_key='testing', port=8080, host='127.0.0.1',