Support refresh token if token is passed to the constructor
Bug #1152427 reported by
Akihiro Motoki
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-neutronclient |
Fix Released
|
Low
|
Oleg Bondarev |
Bug Description
From the discussion in https:/
there is a case where keystone auth is used and auth_token is passed when Client is instantiated.
The following is quoted from my review comment in https:/
----
In the current implementation, when non-None token is passed in the constructor Client(), we also needs to pass end_pointurl, but we don't know the end_pointurl at this point. This behavior of quantumclient is implemented before keystone auth is introduced and we can improve it at the client side.
----
Changed in python-quantumclient: | |
assignee: | nobody → Oleg Bondarev (obondarev) |
Changed in python-quantumclient: | |
status: | New → In Progress |
Changed in python-quantumclient: | |
importance: | Undecided → Low |
Changed in python-neutronclient: | |
milestone: | none → 2.2.1-2.2.6 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/24639
Review: https:/