yahoo-eng-team team mailing list archive

[Dolph Mathews <1476329@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

v3 tokens contain the issued_at and expires_at timestamps for each
token. If a token is created on the v2 API and then validated on the v3
API, this timezone information is missing (the 'Z' at the end of the
timestamp), and thus cannot be validated as ISO 8601 extended format
timestamps.

This patch contains two FIXMEs which, if uncommented, will reproduce
this bug:

  https://review.openstack.org/#/c/203250/

This appears to affect all token formats.

** Affects: keystone
     Importance: Medium
         Status: Triaged

** Description changed:

  v3 tokens contain the issued_at and expires_at timestamps for each
  token. If a token is created on the v2 API and then validated on the v3
  API, this timezone information is missing (the 'Z' at the end of the
  timestamp), and thus cannot be validated as ISO 8601 extended format
  timestamps.
+ 
+ This patch contains two FIXMEs which, if uncommented, will reproduce
+ this bug:
+ 
+   https://review.openstack.org/#/c/203250/

** Description changed:

  v3 tokens contain the issued_at and expires_at timestamps for each
  token. If a token is created on the v2 API and then validated on the v3
  API, this timezone information is missing (the 'Z' at the end of the
  timestamp), and thus cannot be validated as ISO 8601 extended format
  timestamps.
  
  This patch contains two FIXMEs which, if uncommented, will reproduce
  this bug:
  
-   https://review.openstack.org/#/c/203250/
+   https://review.openstack.org/#/c/203250/
+ 
+ This appears to affect all token formats.

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

Title:
  v2 tokens validated on the v3 API are missing timezones

Status in Keystone:
  Triaged

Bug description:
  v3 tokens contain the issued_at and expires_at timestamps for each
  token. If a token is created on the v2 API and then validated on the
  v3 API, this timezone information is missing (the 'Z' at the end of
  the timestamp), and thus cannot be validated as ISO 8601 extended
  format timestamps.

  This patch contains two FIXMEs which, if uncommented, will reproduce
  this bug:

    https://review.openstack.org/#/c/203250/

  This appears to affect all token formats.

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