Putting a secret payload does not fail with an invalid mime-type

Bug #1208601 reported by Melissa Kam
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Barbican
Fix Released
Undecided
John Vrbanac

Bug Description

Steps to Reproduce:
POST http://.../v1/test_tenant/secrets
{
  "name": "AES key",
  "expiration": "2014-02-28T19:14:44.180394",
  "algorithm": "aes",
  "bit_length": 256,
  "cypher_type": "CBC",
  "payload_content_type": "text/plain; charset=utf-8"
}

PUT http://.../v1/test_tenant/secrets/{secret_ref}
{
gF6+lLoF3ohA9aPRpt+6bQ==
}
Headers:
Content-Type: invalid-type

Response:
200 OK

Changed in cloudkeep:
status: New → Confirmed
John Wood (john-wood-w)
Changed in cloudkeep:
status: Confirmed → Fix Committed
Changed in cloudkeep:
assignee: nobody → John Vrbanac (john.vrbanac)
Changed in cloudkeep:
milestone: none → havana-3
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.