Nova requires the deprecated X_USER header in auth mode
Bug #926372 reported by
Gabe Westmaas
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Mark Washenberger |
Bug Description
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/
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.
Changed in nova: | |
milestone: | none → essex-4 |
importance: | Undecided → Medium |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-4 → 2012.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/3775
Review: https:/