diff options
| author | Bruno Semperlotti <bruno.semperlotti@gmail.com> | 2013-04-19 16:22:58 +0200 |
|---|---|---|
| committer | Bruno Semperlotti <bruno.semperlotti@gmail.com> | 2013-05-16 12:12:21 +0200 |
| commit | 840a0758e7dc12360acf83106526436135e8f814 (patch) | |
| tree | 58afa0f464540a061baacfd66d0b3e7b27526bf2 /docs/source | |
| parent | 2e15fe428a2393f786852eb28c26bb9fee166bda (diff) | |
Http 400 when user enabled is not a boolean
When creating or updating a user, no type check was performed on the
enabled attribute. Therefore, if enabled value in JSON/XML is not a
boolean buta string or an int, keystone responds with an incorrect
Http 500 error code and the stacktrace.
The change introduces a type validation of the enabled attribute
at backend and api layer. If the type is not a boolean, keystone
now returns an appropriate Http 400 error code with a message
pointing a bad format for the attribute.
Test cases have been added to file test_backend and
test_content_types for testing the case when enabled attribute is a
string or int when creating or updating user.
The same correction can be done for create/update projects, domains.
Change-Id: I7d2fe3acf0c4dbd3ce5bdf9f4d059df085853b84
Fixes: bug #1110435
Diffstat (limited to 'docs/source')
0 files changed, 0 insertions, 0 deletions