Reviewed: https://review.openstack.org/416372
Committed:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=ec4d0551c0cd3af355a9a64bd2b82c34d538552e
Submitter: Jenkins
Branch: master
commit ec4d0551c0cd3af355a9a64bd2b82c34d538552e
Author: Brant Knudson <bknud...@us.ibm.com>
Date: Tue Jan 3 16:51:25 2017 -0600
Correct timestamp format in token responses
The token issue response has timestamps like this:
"issued_at": "2017-01-03T22:42:55.000000Z"
"expires_at": "2017-01-03T23:42:55.000000Z"
Which didn't match the format documented in the API spec (the
response has subsecond precision and Z rather than ±HHMM).
Change-Id: I1deeac1776a7716ee66d187d1c1c7c1f5b02235f
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
