Hello,
I would think you would want to reuse the same token but update the expiration
time as if it were the first time the token had been generated.
Mark
From: Yongsheng Gong [mailto:gong...@unitedstack.com]
Sent: Friday, August 23, 2013 12:40 AM
To: OpenStack Development Mailing List
On Fri, Aug 23, 2013 at 10:51 AM, Miller, Mark M (EB SW Cloud - RD -
Corvallis) mark.m.mil...@hp.com wrote:
Hello,
** **
I would think you would want to reuse the same token but update the
expiration time as if it were the first time the token had been generated.
That wouldn't work
On Aug 23, 2013 12:24 PM, Dolph Mathews dolph.math...@gmail.com wrote:
On Fri, Aug 23, 2013 at 10:51 AM, Miller, Mark M (EB SW Cloud - RD -
Corvallis) mark.m.mil...@hp.com wrote:
Hello,
I would think you would want to reuse the same token but update the
expiration time as if it were the
On 08/23/2013 12:43 PM, Joe Gordon wrote:
On Aug 23, 2013 12:24 PM, Dolph Mathews dolph.math...@gmail.com
mailto:dolph.math...@gmail.com wrote:
On Fri, Aug 23, 2013 at 10:51 AM, Miller, Mark M (EB SW Cloud - RD
- Corvallis) mark.m.mil...@hp.com mailto:mark.m.mil...@hp.com wrote:
Hi adam,
Can u explain more about 'In conjunction with the caching layer, it might
be the right approach: flush the old tokens upon revocation list
regeneration.'?
when is the list_revoked_tokens called?
thanks
On Sat, Aug 24, 2013 at 1:51 AM, Adam Young ayo...@redhat.com wrote:
On
On Fri, Aug 23, 2013 at 7:48 PM, Yongsheng Gong gong...@unitedstack.comwrote:
Hi adam,
Can u explain more about 'In conjunction with the caching layer, it might
be the right approach: flush the old tokens upon revocation list
regeneration.'?
when is the list_revoked_tokens called?
In a
