Reviewed: https://review.openstack.org/413878
Committed:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=76139d150761e70d34c2b9afb225d57a279a8304
Submitter: Jenkins
Branch: master
commit 76139d150761e70d34c2b9afb225d57a279a8304
Author: jolie <guos...@awcloud.com>
Date: Thu Dec 22 11:10:04 2016 +0800
[api] Inconsistency between v3 API and keystone token timestamps
The v3 API spec for tokens documents the format of timestamps.
It says the format is like "CCYY-MM-DDThh:mm:ss±hh:mm".
By this, the timestamps returned by keystone like this：
2016-12-13T15:33:12+0000
Change-Id: I616865c1b12457487c4aeb5b8e907ca01cb79ef9
Closes-Bug:#1634568
** 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/1634568
Title:
[api] Inconsistency between v3 API and keystone token timestamps
Status in OpenStack Identity (keystone):
Fix Released
Bug description:
The v3 API spec for tokens documents the format of timestamps[1]. It
says the format is like "CCYY-MM-DDThh:mm:ss±hh:mm".
By this, the timestamps returned by keystone should be like
2016-10-17T15:17:03+00:00. But they actually show up like this:
V3:
"issued_at": "2016-10-17T15:17:03.000000Z",
"expires_at": "2016-10-17T16:17:03.000000Z",
V2:
"issued_at": "2016-10-17T15:17:56.000000Z",
"expires": "2016-10-17T16:17:56Z",
Tempest has checks that the timestamp ends in Z.
[1] http://developer.openstack.org/api-ref/identity/v3/?expanded
=validate-and-show-information-for-token-detail#id19
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1634568/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
