© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
Restarting memcached loses revoked token list
----
### Summary ###
When a cloud is deployed using Memcache as a backend for Keystone tokens there is a security concern that restarting Memcached will loose the list of revoked tokens, potentially allowing bad tokens / users to access the system after they had been revoked.
### Affected Services / Software ###
Keystone, Memcache
### Discussion ###
There might be ways to mitigate in the future, such as running memcached on multiple machines to ensure redundancy should the Keystone server fail. In a clustered environment, it will only be an issue if all of the memcached machines shutdown.
Memcachedb might also be a potential way to mitigate. http://
NOTE: Some deployments may intentionally flush Memcached in response to https:/
### Recommended Actions ###
This is a fundamental problem with using in-memory ephemeral storage for security information. If your deployment has strong security requirements or a reliance on up-to-date revoked token information we suggest you consider using an on-disk DB such as MySQL / PostgreSQL or perhaps look into Memcachedb.
### Contacts / References ###
This OSSN : https:/
OpenStack Security ML : openstack-security at lists.openstack.org
OpenStack Security Group : https:/