Brant Knudson da00da732d Fix revoking a scoped token from an unscoped token ... When a scoped token that was created from an unscoped token was revoked, the original token wound up being revoked. This is because the scope wasn't included in the revocation event. By including the scope in the revocation event only the scoped token is revoked. Change-Id: I5652663ab7e1176d3b1efc5d218a8a020498067e Closes-Bug: #1347318		2014-07-29 15:23:24 -05:00
..
backends	Move token persistence classes to token.persistence module	2014-07-24 16:03:50 -07:00
persistence	Move token persistence classes to token.persistence module	2014-07-24 16:03:50 -07:00
providers	Fix revoking a scoped token from an unscoped token	2014-07-29 15:23:24 -05:00
__init__.py	Move token persistence classes to token.persistence module	2014-07-24 16:03:50 -07:00
controllers.py	Consolidate `assert_XXX_enabled` type calls to managers	2014-07-18 10:44:52 -07:00
core.py	Move token persistence classes to token.persistence module	2014-07-24 16:03:50 -07:00
provider.py	Mark the 'check_vX_token' methods deprecated	2014-07-21 21:52:30 +00:00
routers.py	HEAD responses should return same status as GET	2014-07-08 22:37:44 -07:00