Daniel Wagner-Hall 6a4b650d8a Attempt to validate macaroons ... A couple of weird caveats: * If we can't validate your macaroon, we fall back to checking that your access token is in the DB, and ignoring the failure * Even if we can validate your macaroon, we still have to hit the DB to get the access token ID, which we pretend is a device ID all over the codebase. This mostly adds the interesting code, and points out the two pieces we need to delete (and necessary conditions) in order to fix the above caveats.		2015-08-26 13:22:23 +01:00
..
__init__.py	Test ratelimiter	2014-09-02 15:16:26 +01:00
test_auth.py	Attempt to validate macaroons	2015-08-26 13:22:23 +01:00
test_filtering.py	Factor out some of the common homeserver setup code into a	2015-02-11 11:37:30 +00:00
test_ratelimiting.py	Have all unit tests import from our own subclass of trial's unittest TestCase; set up logging in ONE PLACE ONLY	2014-09-12 18:46:13 +01:00