summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChmouel Boudjnah <chmouel@chmouel.com>2012-03-19 14:53:36 +0000
committerChmouel Boudjnah <chmouel@chmouel.com>2012-03-19 16:29:41 +0000
commit2324247baac2ba620da1f6cdc540462e6f0b6a5f (patch)
treeafd00f3846703d29fe1e59128d35da30f7b7db5d
parent7c1e32bba6837eb0937e6e7567aa5e7981db7fec (diff)
downloadkeystone-2324247baac2ba620da1f6cdc540462e6f0b6a5f.tar.gz
keystone-2324247baac2ba620da1f6cdc540462e6f0b6a5f.tar.xz
keystone-2324247baac2ba620da1f6cdc540462e6f0b6a5f.zip
Swift middleware doc update.
Change-Id: I01ecc4d602b5e887f66d32676f11a92d022f693f
-rw-r--r--doc/source/configuringservices.rst13
1 files changed, 8 insertions, 5 deletions
diff --git a/doc/source/configuringservices.rst b/doc/source/configuringservices.rst
index 0faa00ca..b8911570 100644
--- a/doc/source/configuringservices.rst
+++ b/doc/source/configuringservices.rst
@@ -171,13 +171,17 @@ rather than it's built in 'tempauth'.
5. Verify that keystone is providing authentication to Swift
- $ swift -V 2 -A http://localhost:5000/v2.0/tokens -U admin:admin -K ADMIN stat
+ $ swift -V 2 -A http://localhost:5000/v2.0 -U admin:admin -K ADMIN stat
-Configuring Swift with S3 emuluation to use Keystone
-----------------------------------------------------
+.. NOTE::
+ Instead of connecting to Swift here, as you would with other services, we
+ are connecting directly to Keystone.
+
+Configuring Swift with S3 emulation to use Keystone
+---------------------------------------------------
Keystone support validating S3 tokens using the same tokens as the
-generated EC2 tokens. After you have generated a pair of EC2 access
+generated EC2 tokens. When you have generated a pair of EC2 access
token and secret you can access your swift cluster directly with the
S3 api.
@@ -220,7 +224,6 @@ S3 api.
service_host = 127.0.0.1
auth_port = 35357
auth_host = 127.0.0.1
- auth_protocol = http
auth_token = ADMIN
admin_token = ADMIN