This is unfortunately true, but we can't change date formats as it would
be considered an API backwards incompatibility. Hopefully we've made v3
very consistent!
** Changed in: keystone
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1378532
Title:
Keystone token date format is inconsistent
Status in OpenStack Identity (Keystone):
Won't Fix
Bug description:
issued_at field is only in v3, but v2 token response has issued_at.
This is not a major issue. But the format of the date is
inconsistent
"token": {
"expires": "2014-10-08T00:51:35Z",
"id": "a94eec3993a74bf4b26f91bd485f3b6d",
"issued_at": "2014-10-07T20:51:36.005469",
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1378532/+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
