Secrets created via Asymmetric Order do not have a content_type
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Barbican |
Fix Released
|
Low
|
Adam Harwell |
Bug Description
When an Order of type "asymmetric" is submitted, the resulting Secrets do not have content_types attributes in their metadata. This produces inconsistent responses when listing secrets, and also affects client functionality that expects content_types to be available.
Steps to recreate:
POST v1/orders
{
"type": "asymmetric",
"meta": {
"name": "secretname",
"algorithm": "RSA",
"bit_length": 2048,
"expiration": "2015-02-
"payload_
}
}
GET v1/secrets
{
"secrets": [
... SNIP ...
{
"name": "secretname",
},
"mode": "cbc",
},
{
"name": "secretname",
"mode": null,
},
{
"name": "secretname",
"mode": null,
}
],
"total": 5
}
Note how the bottom two secrets do not have "content_types"
Changed in barbican: | |
status: | New → Confirmed |
Changed in barbican: | |
importance: | Undecided → Low |
tags: | added: verified |
Changed in barbican: | |
assignee: | nobody → Adam Harwell (adam-harwell) |
Changed in barbican: | |
status: | In Progress → Fix Committed |
Changed in barbican: | |
milestone: | none → kilo-2 |
Changed in barbican: | |
status: | Fix Committed → Fix Released |
Changed in barbican: | |
milestone: | kilo-2 → 2015.1.0 |
Fix proposed to branch: master /review. openstack. org/142895
Review: https:/