summaryrefslogtreecommitdiff
path: root/test/sample.conf
diff options
context:
space:
mode:
authorPete Zaitcev <zaitcev@kotori.zaitcev.us>2013-03-10 18:52:10 -0600
committerPete Zaitcev <zaitcev@kotori.zaitcev.us>2013-03-10 18:52:10 -0600
commit35e07e2982e129b2f5d225a1de3fdc36c520053e (patch)
treedd06fcfeded775d565d619fe6e878af29cfb6cb0 /test/sample.conf
parent5e427e5e3b41ab2ddb377840f7ea196c1ba7327a (diff)
downloadswift-35e07e2982e129b2f5d225a1de3fdc36c520053e.tar.gz
Permit functional tests against Swift with Keystone
While poking at such problems with authentication other than swauth it was useful to allow stock functional tests running back-to-back at two clusters, with tempauth and Keystone. When running the legacy tests, this version packs account into user the way it was down previously. This way we do not need to repack them before every call to get_auth. The downside is additional work to be done when setting ACLs. Change-Id: Ieb1d9227cb88977ecd2c39825039bc4be8afae0b
Diffstat (limited to 'test/sample.conf')
-rw-r--r--test/sample.conf6
1 files changed, 6 insertions, 0 deletions
diff --git a/test/sample.conf b/test/sample.conf
index d40fb0fe4..49a83f709 100644
--- a/test/sample.conf
+++ b/test/sample.conf
@@ -4,6 +4,12 @@ auth_host = 127.0.0.1
auth_port = 8080
auth_ssl = no
auth_prefix = /auth/
+## sample config for Swift with Keystone
+#auth_version = 2
+#auth_host = localhost
+#auth_port = 5000
+#auth_ssl = no
+#auth_prefix = /v2.0/
# Primary functional test account (needs admin access to the account)
account = test