DefaultCLI plugin doesn't invalidate stored tokens
Bug #1551392 reported by
Jacek Tomasiak
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-keystoneclient |
Won't Fix
|
Undecided
|
Jacek Tomasiak |
Bug Description
Keystone Session's "reauth" feature relies on proper implementation of invalidate() in auth plugins.
DefaultCLI aims to handle typical cases found in CLI client implementations.
As such it is a "combo" plugin which can handle both username/password and token.
If client is called with both of the above, token has higher priority but if it expires, username/password should be used to generate new token for subsequent requests.
The problem is that DefaultCLI doesn't provide custom invalidate() function which would invalidate internally stored token value and enable fallback to username/password.
Changed in python-keystoneclient: | |
assignee: | nobody → Jacek Tomasiak (skazi) |
status: | New → Confirmed |
To post a comment you must log in.
please ensure that this is also the case for 'python- openstackclient ' (which is a new unified CLI) as the CLI that is bundled with 'python- keystoneclient' is deprecated and will be removed in the N release.