Can't get a trust-scoped token via v2 client
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-keystoneclient |
Fix Released
|
Wishlist
|
Steven Hardy | ||
tempest |
Won't Fix
|
Wishlist
|
Unassigned |
Bug Description
It should be possible to authenticate a v2 client with a trust ID, as this request is valid (discovered after digging in the v2 controller code, I don't think this is documented anywhere yet?)
"auth": {
"token": {
"id": "68f720c6434946
},
}
There are a few strings attached:
- You can't use username/password, you have to get a token first, then get it re-scoped
- When the trust has impersonation=
Then you can do a call like this:
c_trust_v2 = client_
ret = c_trust_
After this (with the patch I'm about to post), you have auth_ref correctly trust_scoped for the v2 client.
Changed in python-keystoneclient: | |
assignee: | nobody → Steven Hardy (shardy) |
Changed in python-keystoneclient: | |
milestone: | none → 0.3.3 |
importance: | Undecided → Wishlist |
Changed in python-keystoneclient: | |
milestone: | 0.3.3 → none |
Changed in python-keystoneclient: | |
milestone: | none → 0.4.1 |
Changed in python-keystoneclient: | |
status: | Fix Committed → Fix Released |
Changed in tempest: | |
importance: | Undecided → Wishlist |
Fix proposed to branch: master /review. openstack. org/48462
Review: https:/