Incorrect HTTP response for POST /v2.0/tokens scenarios

[Rohit Karajgi]

Keystone returns HTTP 401 Not Authorized when it should return 400 Bad Request for the below use case:

{
    "auth": {
          "passwordCredentials": {
                    "password": "pass" # Do not pass username or password Key or both (blank dict for for passwordCredentials)
           },
           "tenantName": "demo"
     }
}
Actual response: 401 Not Authorized
Expected response: 400 Bad Request

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/14328

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/14328
Committed: http://github.com/openstack/keystone/commit/7ac4d521103afa80c8f69c6b214a227c6a9346e3
Submitter: Jenkins
Branch: master

commit 7ac4d521103afa80c8f69c6b214a227c6a9346e3
Author: Unmesh Gurjar <email address hidden>
Date: Thu Oct 11 03:49:28 2012 -0700

    Fixes response for missing credentials in auth

    1. If username or password parameters are not specified in the authentication
    request, API returns 401 response. Fixed this to return a 400 Bad Request
    instead.
    2. Also added unit test coverage.

    Fixes LP: #1060723

    Change-Id: I4861d5b989a151d8fce20f012bb0878b06b9b559