yahoo-eng-team team mailing list archive

["jun923.gu" <1899876@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

We encounter this situation that MEMOIZE_TOKENS decorator will set token
to cache when validating token. We take a deeper look at the cache codes
and found that dogpile will call get_or_create function. That is, if
fail to get token from cache, dogpile will set token to cache. As we
config CONF.token.cache_on_issue to False, we would not wish token
setted into cache.

** Affects: keystone
     Importance: Undecided
         Status: New

** Description changed:

  We encounter this situation that MEMOIZE_TOKENS decorator will set token
  to cache when validating token. We take a deeper look at the cache codes
  and found that dogpile will call get_or_create function. That is, if
  fail to get token from cache, dogpile will set token to cache. As we
  config CONF.token.cache_on_issue to False, we would not wish token
- setted to cache.
+ setted into cache.

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1899876

Title:
  MEMOIZE_TOKENS set token to cache when validating token

Status in OpenStack Identity (keystone):
  New

Bug description:
  We encounter this situation that MEMOIZE_TOKENS decorator will set
  token to cache when validating token. We take a deeper look at the
  cache codes and found that dogpile will call get_or_create function.
  That is, if fail to get token from cache, dogpile will set token to
  cache. As we config CONF.token.cache_on_issue to False, we would not
  wish token setted into cache.

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