move s3_token middleware to keystoneclient
Bug #1178741 reported by
Adam Young
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Wishlist
|
Brant Knudson | ||
python-keystoneclient |
Fix Released
|
Wishlist
|
Brant Knudson |
Bug Description
s3_token middleware is in keystone, and needs to be moved to the keystoneclient project just like we moved the auth_token middleware.
Changed in keystone: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in keystone: | |
importance: | Medium → Wishlist |
Changed in python-keystoneclient: | |
importance: | Undecided → Wishlist |
Changed in python-keystoneclient: | |
assignee: | nobody → Brant Knudson (blk-u) |
status: | New → In Progress |
Changed in python-keystoneclient: | |
milestone: | none → 0.5.0 |
Changed in python-keystoneclient: | |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
assignee: | nobody → Brant Knudson (blk-u) |
Changed in keystone: | |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | icehouse-3 → 2014.1 |
To post a comment you must log in.
The following proposal will address the issue mentioned in the bug.
https:/ /blueprints. launchpad. net/keystone/ +spec/generic- signature- validation