Checking for generating header is wrong
Bug #1307899 reported by
Masahito Muroi
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-heatclient |
Won't Fix
|
Undecided
|
Masahito Muroi | ||
Bug Description
If heatclient.Client class is instanced with username, password and token, api call by the Client doesn't succeed.
Heat requires api clients to add X-Auth-User and X-Auth-Key in API request header.
However, if heatclient.Client has username, password and token and without include_pass, the two headers aren't generated and fails to call heat api though arguments of the client is collect.
| Changed in python-heatclient: | |
| assignee: | nobody → Masahito Muroi (muroi-masahito) |
Revision history for this message
| Steve Baker (steve-stevebaker) wrote | #1 |
| Changed in python-heatclient: | |
| status: | New → Won't Fix |
To post a comment you must log in.
When heat uses trusts for deferred auth the X-Auth-User and X-Auth-Key are not required. We don't want to pass X-Auth-User and X-Auth-Key unless absolutely necessary, hence the include_pass option.
Soon trusts will be the default, so include_pass only remains as an option to support older versions of heat.