[api] Inconsistency between v3 API and keystone token timestamps
Bug #1634568 reported by
Brant Knudson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Low
|
Brant Knudson |
Bug Description
The v3 API spec for tokens documents the format of timestamps[1]. It says the format is like "CCYY-MM-
By this, the timestamps returned by keystone should be like 2016-10-
V3:
"issued_at": "2016-10-
"expires_at": "2016-10-
V2:
"issued_at": "2016-10-
"expires": "2016-10-
Tempest has checks that the timestamp ends in Z.
Changed in keystone: | |
assignee: | nobody → Praveen N (praveenn) |
Changed in keystone: | |
milestone: | none → ocata-1 |
importance: | Undecided → High |
Changed in keystone: | |
assignee: | nobody → Kalaswan Datta (kalaswan-datta) |
Changed in keystone: | |
milestone: | ocata-1 → ocata-2 |
tags: | added: api-ref |
summary: |
- Inconsistency between v3 API and keystone token timestamps + [api] Inconsistency between v3 API and keystone token timestamps |
Changed in keystone: | |
importance: | Undecided → Low |
Changed in keystone: | |
assignee: | nobody → guoshan (guoshan) |
Changed in keystone: | |
milestone: | none → ocata-3 |
To post a comment you must log in.
Since this is a v2-ism, we should be able to apply an easy fix to the v3_to_v2_token method [0]. This will keep the v2 behavior isolated to v2.0 token code.
[0] https:/ /github. com/openstack/ keystone/ blob/4ac5cb9274 86a3461255f30c8 6c1cd9df4d46f16 /keystone/ token/providers /common. py#L119