Auth_token middleware should cope with no response from "Get versions"
Bug #1154072 reported by
Henry Nash
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-keystoneclient |
Invalid
|
Wishlist
|
Unassigned | ||
Bug Description
The new auth_token supports both v2 and v3 api versions. In order to ascertain which version to use, it queries the server for a list of supported versions (and then chooses the highest compatible version). Some installations might block such a query of supported versions, so if such a call fails, auth_token should attempt to use the lowest version it understands. It is already possible to force auth_token to use a specific version (by setting auth_version), so the combination of these two approaches should cover most, if not all, eventualities
| summary: |
- Auth_token middleware should copy with no response from "Get versions" + Auth_token middleware should cope with no response from "Get versions" |
| Changed in keystone: | |
| importance: | Medium → Wishlist |
| assignee: | Henry Nash (henry-nash) → nobody |
| affects: | keystone → python-keystoneclient |
| Changed in python-keystoneclient: | |
| status: | New → Triaged |
Revision history for this message
| Steve Martinelli (stevemar) wrote | #1 |
| Changed in python-keystoneclient: | |
| status: | Triaged → Invalid |
To post a comment you must log in.
this is now done in keystonemiddleware and we fall back to both v2 and v3 auth strategy if none is supplied:
https:/
marking as invalid