Add support for using pre-existing token and Keystone URL
Bug #1213052 reported by
Jiří Stránský
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-tuskarclient |
Won't Fix
|
Low
|
Unassigned | ||
Bug Description
Currently two authentication methods are supported:
* username + password + tenant + Keystone URL
* token + Tuskar URL
A third method would make sense for some use cases:
* token + Keystone URL (in this scenario, we would re-use existing token, but use Keystone to fetch Tuskar's URL)
| Changed in python-tuskarclient: | |
| importance: | Undecided → Low |
| Changed in python-tuskarclient: | |
| status: | New → Triaged |
| Changed in python-tuskarclient: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
