ec2 signature validation fails with v3 credentials
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Medium
|
Steven Hardy |
Bug Description
If you create an ec2 keypair via the v3/credentials API:
Then you get a 500 when trying to validate a signed request (signed using the keypair) via the ec2tokens extension:
2013-12-10 14:52:30.060 722 ERROR keystone.
2013-12-10 14:52:30.060 722 TRACE keystone.
2013-12-10 14:52:30.060 722 TRACE keystone.
2013-12-10 14:52:30.060 722 TRACE keystone.
2013-12-10 14:52:30.060 722 TRACE keystone.
2013-12-10 14:52:30.060 722 TRACE keystone.
2013-12-10 14:52:30.060 722 TRACE keystone.
2013-12-10 14:52:30.060 722 TRACE keystone.
2013-12-10 14:52:30.060 722 TRACE keystone.
2013-12-10 14:52:30.060 722 TRACE keystone.
2013-12-10 14:52:30.060 722 TRACE keystone.
It looks like a mismatch between the way the data blob is stored via v3/credentials and creating the keypair direct via the ec2tokens
Changed in keystone: | |
assignee: | nobody → Steven Hardy (shardy) |
Changed in keystone: | |
importance: | Undecided → Medium |
Changed in keystone: | |
milestone: | none → icehouse-2 |
status: | Fix Committed → Fix Released |
tags: | added: havana-backport-potential |
Changed in keystone: | |
milestone: | icehouse-2 → 2014.1 |
Fix proposed to branch: master /review. openstack. org/66445
Review: https:/