Nova requires the deprecated X_USER header in auth mode

[Gabe Westmaas]

When using NovaKeystoneContext middleware, nova requires the use of the X_USER header instead of the X_USER_ID header. When using only the X_USER_ID header, client sees:

401 Unauthorized

This server could not verify that you are authorized to access the document you requested. Either you supplied the wrong credentials (e.g., bad password), or your browser does not understand how to supply the credentials required.

In nova logs:
2012-02-03 15:20:50,038 DEBUG nova [-] X_USER not found in request from (pid=25727) __call__ /usr/lib/python2.6/dist-packages/nova/api/auth.py:62

user id in context should be set to X_USER_ID first and if that isn't there (in the case of an older client) X_USER.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/3775
Committed: http://github.com/openstack/nova/commit/f0a11485894f56aba337f65af5f92bede12ef17f
Submitter: Jenkins
Branch: master

commit f0a11485894f56aba337f65af5f92bede12ef17f
Author: Mark Washenberger <email address hidden>
Date: Fri Feb 3 17:31:35 2012 -0500

    X_USER is deprecated in favor of X_USER_ID

    Addressed bug 926372

    Eventually, we should stop supporting X_USER because it is *supposed* to
    be the user's login name rather than their id. But this change preserves
    the old behavior for stability.

    For more info checkout keystone/middleware/auth_token.py in the keystone
    project.

    Change-Id: Ie837e73f9a592a903af71a426e202f8b6a9ac581