Chris Dent d3352ff422 Identify the keystone service when raising 503 ... When the keystonemiddleware is used directly in the WSGI stack of an application, the 503 that is raised when the keystone service errors or cannot be reached needs to identify that keystone is the service that has failed, otherwise it appears to the client that it is the service they are trying to access is down, which is misleading. This addresses the problem in the most straightforward way possible: the exception that causes the 503 is given a message including the word "Keystone". The call method in BaseAuthTokenTestCase gains an expected_body_string kwarg. If not None, the response body (as a six.text_type) is compared with the value. Change-Id: Idf211e7bc99139744af232f5ea3ecb4be41551ca Closes-Bug: #1747655 Closes-Bug: #1749797		2018-02-20 17:32:41 +01:00
..
audit	Fix oslo.messaging deprecation of get_transport	2017-05-24 22:14:07 -05:00
auth_token	Identify the keystone service when raising 503	2018-02-20 17:32:41 +01:00
__init__.py	Move unit tests into tests.unit	2015-03-11 17:03:54 -05:00
client_fixtures.py	Fix gate error caused by mocked URLs	2017-09-25 10:01:04 -05:00
test_ec2_token_middleware.py	Fix D204 PEP257 violation and enable D301 and D209	2016-05-06 16:36:15 +00:00
test_entry_points.py	Define entry points for filter factories for Paste Deployment	2015-11-06 12:16:44 -06:00
test_fixtures.py	Add project_name to the auth_token fixture	2016-01-13 15:10:36 +11:00
test_opts.py	Rename auth_uri to www_authenticate_uri	2017-10-11 14:00:49 +02:00
test_s3_token_middleware.py	Rename auth_uri to www_authenticate_uri	2017-10-11 14:00:49 +02:00
utils.py	use oslo.log instead of logging	2017-01-13 03:24:18 +00:00