Glance Registry: No way to use Context middleware without keystone auth_token middleware
Bug #1199990 reported by
Alex Meade
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Fix Released
|
High
|
Alex Meade |
Bug Description
The Context middleware depends on a number of request headers being present. Typically, the auth_token middleware will query keystone with an auth token and then construct teh necessary headers.
Glance api needs to be able to send these headers incase we want to have an authenticated user in glance registry without querying auth for user information via auth_token middleware.
These headers are:
'X-User-Id
X-Tenant-Id
X-Roles
X-Identity-Status
X-Service-Catalog
Changed in glance: | |
milestone: | none → havana-3 |
status: | Fix Committed → Fix Released |
Changed in glance: | |
milestone: | havana-3 → 2013.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/36563
Review: https:/