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
This commit is contained in:
parent
663865dfec
commit
ec4d0551c0
|
@ -291,12 +291,9 @@ token_expires:
|
|||
|
||||
::
|
||||
|
||||
CCYY-MM-DDThh:mm:ss±hhmm
|
||||
CCYY-MM-DDThh:mm:ss.sssZ
|
||||
|
||||
For example, ``2015-08-27T09:49:58-0500``.
|
||||
|
||||
The ``±hhmm`` value, if included, is the time zone as an offset
|
||||
from UTC. In the previous example, the offset value is ``-0500``.
|
||||
For example, ``2015-08-27T09:49:58.000000Z``.
|
||||
|
||||
A ``null`` value indicates that the token never expires.
|
||||
in: body
|
||||
|
@ -317,12 +314,9 @@ token_issued_at:
|
|||
|
||||
::
|
||||
|
||||
CCYY-MM-DDThh:mm:ss±hhmm
|
||||
CCYY-MM-DDThh:mm:ss.sssZ
|
||||
|
||||
For example, ``2015-08-27T09:49:58-0500``.
|
||||
|
||||
The ``±hhmm`` value, if included, is the time zone as an offset
|
||||
from UTC. In the previous example, the offset value is ``-0500``.
|
||||
For example, ``2015-08-27T09:49:58.000000Z``.
|
||||
in: body
|
||||
required: true
|
||||
type: string
|
||||
|
|
|
@ -70,12 +70,9 @@ expires:
|
|||
|
||||
::
|
||||
|
||||
CCYY-MM-DDThh:mm:ss±hhmm
|
||||
CCYY-MM-DDThh:mm:ss.sssZ
|
||||
|
||||
For example, ``2015-08-27T09:49:58-0500``.
|
||||
|
||||
The ``±hhmm`` value, if included, is the time zone as an offset
|
||||
from UTC. In the previous example, the offset value is ``-0500``.
|
||||
For example, ``2015-08-27T09:49:58.000000Z``.
|
||||
|
||||
A ``null`` value indicates that the token never expires.
|
||||
in: body
|
||||
|
@ -103,12 +100,9 @@ issued_at:
|
|||
|
||||
::
|
||||
|
||||
CCYY-MM-DDThh:mm:ss±hhmm
|
||||
CCYY-MM-DDThh:mm:ss.sssZ
|
||||
|
||||
For example, ``2015-08-27T09:49:58-0500``.
|
||||
|
||||
The ``±hhmm`` value, if included, is the time zone as an offset
|
||||
from UTC. In the previous example, the offset value is ``-0500``.
|
||||
For example, ``2015-08-27T09:49:58.000000Z``.
|
||||
in: body
|
||||
required: true
|
||||
type: string
|
||||
|
|
|
@ -921,12 +921,9 @@ expires_at:
|
|||
|
||||
::
|
||||
|
||||
CCYY-MM-DDThh:mm:ss±hhmm
|
||||
CCYY-MM-DDThh:mm:ss.sssZ
|
||||
|
||||
For example, ``2015-08-27T09:49:58-0500``.
|
||||
|
||||
The ``±hhmm`` value, if included, is the time zone as an offset
|
||||
from UTC. In the previous example, the offset value is ``-0500``.
|
||||
For example, ``2015-08-27T09:49:58.000000Z``.
|
||||
|
||||
A ``null`` value indicates that the token never expires.
|
||||
in: body
|
||||
|
@ -1094,12 +1091,9 @@ issued_at:
|
|||
|
||||
::
|
||||
|
||||
CCYY-MM-DDThh:mm:ss±hhmm
|
||||
CCYY-MM-DDThh:mm:ss.sssZ
|
||||
|
||||
For example, ``2015-08-27T09:49:58-0500``.
|
||||
|
||||
The ``±hhmm`` value, if included, is the time zone as an offset
|
||||
from UTC. In the previous example, the offset value is ``-0500``.
|
||||
For example, ``2015-08-27T09:49:58.000000Z``.
|
||||
in: body
|
||||
required: true
|
||||
type: string
|
||||
|
|
Loading…
Reference in New Issue