v3/ec2tokens validation results in v2 token
Bug #1269947 reported by
Steven Hardy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
High
|
Morgan Fainberg |
Bug Description
The ec2tokens extension is available in the default paste pipeline for both v2 and v3 API, but it's the same controller and it returns v2 tokens via both paths.
We probably need to refactor to remove the v3 compatibility mangling in the existing ec2tokens implementation and provide a proper v3 ported version which returns v3 format tokens when validating signed requests.
Changed in keystone: | |
assignee: | nobody → Morgan Fainberg (mdrnstm) |
status: | Triaged → In Progress |
Changed in keystone: | |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | icehouse-3 → 2014.1 |
To post a comment you must log in.
Eek, I'm thinking we should remove the v2 middleware from the v3 pipeline as a first step to addressing this?