When using v3 API to authenticate user/password in XML format, should report 400 Bad request instead of 401 if the XML if malformed
Bug #1179765 reported by
xingzhou
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Expired
|
Medium
|
Unassigned |
Bug Description
when using the request like below:
curl -i -X POST -H "X-Auth-
knowing that in the above request xml, there should be domain specified, the v3 API respond with 401 unauthorized error, which should be 400 bad request if the XML is malformed. 401 would lead to confusion
tags: | removed: grizzly-backport-potential |
To post a comment you must log in.
This doesn't look like valid usage of the authentication API, as an unnecessary X-Auth-Token is being provided in the request headers. If this issue is still reproducible without that header, then this should certainly be fixed.