Brant Knudson ec4d0551c0 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		2017-01-04 13:05:23 -06:00
..
samples/admin	Document OS-SIMPLE-CERT Routes	2016-11-01 08:26:00 -04:00
admin-certificates.inc	Document OS-SIMPLE-CERT Routes	2016-11-01 08:26:00 -04:00
admin-endpoints.inc	Refactor Keystone admin-endpoint API	2016-09-20 10:29:31 +07:00
admin-tenants.inc	Refactor Keystone admin-tenant API v2	2016-09-20 10:30:22 +07:00
admin-tokens.inc	Refactor Keystone admin-tokens and admin-users v2	2016-11-28 18:18:39 +07:00
admin-users.inc	Refactor Keystone admin-tokens and admin-users v2	2016-11-28 18:18:39 +07:00
admin-versions.inc	Correct normal response codes in v2.0 versions doc	2016-07-13 19:56:24 +00:00
index.rst	Document OS-SIMPLE-CERT Routes	2016-11-01 08:26:00 -04:00
parameters.yaml	Correct timestamp format in token responses	2017-01-04 13:05:23 -06:00