yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #47730
[Bug 1476329] Re: v2 tokens validated on the v3 API are missing timezones
Reviewed: https://review.openstack.org/290139
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=dced6805a2628742e63516f4730e191e595ad10b
Submitter: Jenkins
Branch: master
commit dced6805a2628742e63516f4730e191e595ad10b
Author: werner mendizabal <nonameentername@xxxxxxxxx>
Date: Tue Mar 8 15:20:05 2016 -0600
v2 tokens validated on the v3 API are missing timezones
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 appears to affect all token formats.
Change-Id: Ibf0e65852a010c595e9f1154695d3884549d2cbc
Closes-Bug: #1476329
** Changed in: keystone
Status: In Progress => Fix Released
--
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/1476329
Title:
v2 tokens validated on the v3 API are missing timezones
Status in OpenStack Identity (keystone):
Fix Released
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
References