StackTrace on 2012.1.4 middleware when storing token in memcache with SWIFT 1.7.4

[Alejandro Comisario]

when integrating Keystone 2012.1.4 with SWIFT, and swift-proxy is configured to cache tokens in memcache, we get a response "500 internal server error" from swift because keystone.middleware.auth_token stacktraces with :
"TypeError: %d format: a number is required, not str" in two situations.

#1 when a new token wants to be cached
#2 when an invalid ( non existent or expired ) token is cached

For the #1 & #2 cases, we patched /usr/local/lib/python2.7/dist-packages/keystone-2012.1.[VERS]-py2.7.egg/keystone/middleware/auth_token.py in the line 151 and replaced :

self.token_cache_time = conf.get('token_cache_time', 300)
with
self.token_cache_time = int(conf.get('token_cache_time', 300))

We think its a big and anoying bug when you need this feature from keystone ( most of serious SWIFT implementations )
Thanks !!

[Davanum Srinivas (DIMS) (dims-v)]

Already fixed in grizzly

https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/middleware/auth_token.py#L285

[Dolph Mathews (dolph)]

Installing the latest version of python-keystoneclient and using keystoneclient.middleware.auth_token instead of keystone.middleware.auth_token from essex or folsom should be a viable workaround.