keystone/keystone/token
Arvind Tiwari f1f0bbc4b4 Validate token calls return 404 on invalid tokens
Invalid X-Subject-Token was resulting in HTTP 401 rather than 404
This is causing the auth_token middleware to re-authenticate
It expects a 404 on an invalid token.

Change-Id: Ieb4cbd4f69b4f3c5944eebc262e694e831d1ca6d
Fixed-Bug: #1221889
Fixed-Bug: #1186059
2013-09-26 15:12:21 -07:00
..
backends Changed header from LLC to Foundation based on trademark policies 2013-09-05 15:03:32 -05:00
providers Validate token calls return 404 on invalid tokens 2013-09-26 15:12:21 -07:00
__init__.py Changed header from LLC to Foundation based on trademark policies 2013-09-05 15:03:32 -05:00
controllers.py Cleanup of tenantId, tenant_id, and default_project_id 2013-09-22 17:36:02 -07:00
core.py Ensure v2 tokens are correctly invalidated when using BelongsTo 2013-09-19 16:22:25 +01:00
provider.py Validate token calls return 404 on invalid tokens 2013-09-26 15:12:21 -07:00
routers.py Changed header from LLC to Foundation based on trademark policies 2013-09-05 15:03:32 -05:00