Attempting to get a text/plain secret from a created order should return a 406
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Barbican |
Fix Released
|
High
|
Bryan D. Payne |
Bug Description
When we attempt to get the plain/text secret payload from a freshly created order we get a 500 internal server error.
Steps to replicate:
1) Create an order:
Request:
{
"secret": {
"name": "secretname",
"algorithm": "aes",
"payload_
"payload_
"mode": "cbc",
"bit_length": 256
}
}
2) Get the order:
Response:
{
"status": "ACTIVE",
"secret_ref": "http://{host}/
"updated": "2013-09-
"created": "2013-09-
"secret": {
"name": "secretname",
"algorithm": "aes",
"payload_
"expiration": null,
"bit_length": 256,
"mode": "cbc"
},
"order_ref": "http://{host}/
}
3) Get Secret:
Request:
GET '/v1/test_
Headers:
'Content-Type': 'application/json',
'Accept': 'text/plain',
'User-Agent': 'python-
Expected Response: 406
Actual Response: 500
Changed in cloudkeep: | |
importance: | Undecided → High |
milestone: | none → havana |
assignee: | nobody → John Wood (john-wood-w) |
assignee: | John Wood (john-wood-w) → nobody |
Changed in cloudkeep: | |
status: | New → Fix Committed |
Changed in barbican: | |
milestone: | havana → icehouse-1 |
Changed in barbican: | |
status: | Fix Committed → Fix Released |
I have a fix working for this. I'll polish it up with tests and such and submit a PR early next week.