Description of problem: https://bugs.launchpad.net/keystone/+bug/1020127/comments/14 "you *must* set this option (cache=swift.cache) if you are using auth_token in a swift proxy server." Requires backport of https://github.com/openstack/python-keystoneclient/commit/62be31419f3a8765407ad583110fc7d36fb64dcf
Verified with python-keystoneclient-0.2.3-2.el6ost. When cache = swift.cache is set in filter:authtoken section of swift/proxy-server.conf, authtoken m/w in proxy-server reports that it will use memcache from swift.cache. Settings just memcache_servers (direct memcached for authtoke, instead of inheriting it from swift) does not works as parsing of that option fails, but should be caused by different change and so was moved to bug #971497.
(In reply to Pavel Sedlák from comment #6) > Settings just memcache_servers (direct memcached for authtoke, instead of > inheriting it from swift) does not works as parsing of that option fails, Direct memcached probably doesn't make sense within Swift, so that's not critical, but we can discuss that in the cloned bug 971497.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0944.html