Error message for bad bit length is insufficient on secret create
Bug #1386251 reported by
Steve Heyman
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Barbican |
Fix Released
|
Low
|
Juan Antonio Osorio Robles |
Bug Description
When you create a secret with an invalid bit length you get back an error 400 but the text of the message doesn't indicate that the bit_length is the culprit. It simply says that a field is not of type integer but it doesn't indicate what that field is.
It should function like TypeOrders's validation for bit length.
Changed in barbican: | |
status: | New → Confirmed |
importance: | Undecided → Low |
Changed in barbican: | |
assignee: | nobody → N Dillon (sicarie) |
Changed in barbican: | |
assignee: | N Dillon (sicarie) → nobody |
Changed in barbican: | |
assignee: | nobody → pradeep kumar singh (pradeep-singh-u) |
Changed in barbican: | |
assignee: | pradeep kumar singh (pradeep-singh-u) → nobody |
Changed in barbican: | |
assignee: | nobody → Juan Antonio Osorio Robles (juan-osorio-robles) |
Changed in barbican: | |
status: | Confirmed → In Progress |
Changed in barbican: | |
milestone: | none → liberty-3 |
status: | Fix Committed → Fix Released |
Changed in barbican: | |
milestone: | liberty-3 → 1.0.0 |
To post a comment you must log in.
This appears to still be an issue.