I asked this question in different thread but no response. Why does keystone not re-use the token the one it has already issued for the same credentials. Any reason for not doing that? Thanks, -Ravi. On Wed, Jun 12, 2013 at 11:04 AM, Jay Pipes <jaypipes at gmail.com> wrote: > On 06/12/2013 12:54 PM, Craig E. Ward wrote: > >> I am working with a Folsom installation of OpenStack. The Keystone >> database (mysql) gets very large. The token table has millions of rows >> of expired tokens. Is there a reason not to delete these from the table? >> > > Not unless you need them for some security auditing purpose... and if you > don't, I recommend switching to the memcache token driver. It's faster and > doesn't have the drawback of filling up your identity database will > millions of token records. > > best, > -jay > > > > ______________________________**_________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.**org <OpenStack-dev at lists.openstack.org> > http://lists.openstack.org/**cgi-bin/mailman/listinfo/**openstack-dev<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev> > -- Ravi -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130614/18f46c7c/attachment.html>