yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1202053] Re: Memcache token backend issue upgrading from Grizzly

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Launchpad Bug Tracker <1202053@xxxxxxxxxxxxxxxxxx>
Date: Mon, 29 Sep 2014 04:19:22 -0000
Reply-to: Bug 1202053 <1202053@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

[Expired for Keystone because there has been no activity for 60 days.]

** Changed in: keystone
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1202053

Title:
  Memcache token backend issue upgrading from Grizzly

Status in OpenStack Identity (Keystone):
  Expired

Bug description:
  Noticed a possible upgrade issue with the pluggable token provider change:
  https://github.com/openstack/keystone/commit/c238ace30981877e5991874c5b193ea7d5107419#L12L121

  If old PKI tokens still live in a usertoken- index value in memcache,
  keystone will try to use them as a key to get the actual token. Since
  they're > 256 bytes this will likely raise an error and make token
  creation fail for any user with an old token.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1202053/+subscriptions