auth_token middleware should properly handle KeyError
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Critical
|
Dan Prince |
Bug Description
Running devstack, completely clean installation of all components.
Get this:
ubuntu@
Failed to show index. Got error:
Internal Server error: Traceback (most recent call last):
File "/usr/lib/
result = self.applicatio
File "/usr/lib/
resp = self.call_func(req, *args, **self.kwargs)
File "/usr/lib/
return self.func(req, *args, **kwargs)
File "/opt/stack/
response = req.get_
File "/usr/lib/
application, catch_exc_
File "/usr/lib/
app_iter = application(
File "/opt/stack/
valid = self._validate_
File "/opt/stack/
self.
File "/opt/stack/
return json.loads(
KeyError: 'access'
Both Nati Ueno and I can verify this behaviour...
At a minimum, the auth_token middleware should never simply barf a KeyError. Too many assumptions are made about the response JSON in the _get_admin_
Changed in keystone: | |
milestone: | none → essex-4 |
Changed in keystone: | |
assignee: | nobody → Ben McGraw (mcgrue) |
summary: |
- Admin token auth completely broken + auth_token middleware should properly handle KeyError |
Changed in keystone: | |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | essex-4 → 2012.1 |
I got this error in keystone log.
2012-02-28 06:03:41 WARNING [root] Invalid user / password ******* ****** RESPONSE HEADERS ******* ******* ****** ******* ****** RESPONSE BODY ******* ******* ******
2012-02-28 06:03:41 DEBUG [root] *******
2012-02-28 06:03:41 DEBUG [root] Content-Type = application/json
2012-02-28 06:03:41 DEBUG [root] Content-Length = 89
2012-02-28 06:03:41 DEBUG [root]
2012-02-28 06:03:41 DEBUG [root] *******
2012-02-28 06:03:41 DEBUG [root] {"error": {"message": "Invalid user / password", "code": 401, "title": "Not Authorized"}}