Update documentation to use keystoneauth name
Update documentation to use keystoneauth in the proxy server pipeline. Change 5e372016 added
pipeline checking and explicitly looks for keystoneauth name, so README should match.
Also update package name for s3_token middleware to be keystoneclient, not keystone.
Closes-Bug: #1381758
Change-Id: I0d769e47ffc32725c1df2def4d9d46c25474132e
This commit is contained in:
@@ -35,7 +35,10 @@ If you use keystone:
|
||||
Change To::
|
||||
|
||||
[pipeline:main]
|
||||
pipeline = catch_errors cache swift3 s3token authtoken keystone proxy-server
|
||||
pipeline = catch_errors cache swift3 s3token authtoken keystoneauth proxy-server
|
||||
|
||||
Note that swift3 explicitly checks that keystoneauth is in the pipeline. You must use this name
|
||||
in the pipeline statement and in [filter:keystoneauth] section header.
|
||||
|
||||
3) Add to your proxy-server.conf the section for the Swift3 WSGI filter::
|
||||
|
||||
@@ -45,7 +48,7 @@ If you use keystone:
|
||||
You also need to add the following if you use keystone (adjust port, host, protocol configurations for your environment):
|
||||
|
||||
[filter:s3token]
|
||||
paste.filter_factory = keystone.middleware.s3_token:filter_factory
|
||||
paste.filter_factory = keystoneclient.middleware.s3_token:filter_factory
|
||||
auth_port = 35357
|
||||
auth_host = 127.0.0.1
|
||||
auth_protocol = http
|
||||
|
||||
Reference in New Issue
Block a user