yahoo-eng-team team mailing list archive

[Brant Knudson <bknudson@xxxxxxxxxx>]

Public bug reported:

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

** Affects: keystone
     Importance: Undecided
         Status: New

-- 
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:
  Inconsistency between v3 API and keystone token timestamps

Status in OpenStack Identity (keystone):
  New

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