Can't Authenticate users not in Keystone default domain
Bug #1299807 reported by
Phil Day
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-neutronclient |
Fix Released
|
Low
|
Phil Day |
Bug Description
The Keystone V3 API allows users to be created in Domains. To authenticate such a user via the V2 API (which is the only version supported currently by the client) you have to authenticate by ID rather than name. Tenant ID auth is already supported, but user ID isn't.
Adding support for User ID base auth would be a good short term step ahead of adding support for Keystone V3 API
Changed in python-neutronclient: | |
assignee: | nobody → Phil Day (philip-day) |
status: | New → In Progress |
Changed in python-neutronclient: | |
importance: | Undecided → Low |
milestone: | none → 2.3.5 |
Changed in python-neutronclient: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/78596 /git.openstack. org/cgit/ openstack/ python- neutronclient/ commit/ ?id=ed5ea512ca4 81478c95f3bc0f8 120d102e4da9c7
Committed: https:/
Submitter: Jenkins
Branch: master
commit ed5ea512ca48147 8c95f3bc0f8120d 102e4da9c7
Author: Phil Day <email address hidden>
Date: Thu Mar 6 13:07:49 2014 +0000
Allow user ID for authentication
In Keystone V3 user names are no longer necessarily unique
across domains.
A user can still authenticate a user in the non default
domain via the V2 API providng they use IDs instead of names.
Tenant_ID is already supported, this change adds support
for user ID
Closes-Bug: #1299807
Change-Id: I22fdd9a6749f7d fbdd2dc8313fddc 81e5ea0b753