Steven Hardy 8fcc18c42b Fix v2 token user ref with trust impersonation=True ... The v2 token controller incorrectly checks for a string instead of a boolean, which results in the wrong user ID (trustee, when it should be the trustor) when impersonation=True. So fix the comparison and tests, adding a test which illustrates the issue. This patchset also closes the gap that allows EC2 credentials to be issued from trust-scoped tokens, allowing privilege escalation since EC2 tokens have no concept of trust-scoping/role restrictions in the Grizzly release. Change-Id: Ic94f30f2354c9fda20531bb598387368fde8a096 Closes-Bug: #1239303 Related-Bug: #1242597		2013-12-13 14:02:15 -08:00
..
access	Generate apache-style common access logs	2013-01-31 08:16:21 -06:00
admin_crud	tenant to project in the apis	2013-01-28 16:48:53 -05:00
ec2	Fix v2 token user ref with trust impersonation=True	2013-12-13 14:02:15 -08:00
s3	Expose auth failure details in debug mode	2012-11-20 15:43:28 -06:00
stats	Fixes import order nits	2013-01-11 09:05:11 +08:00
user_crud	Fixes import order nits	2013-01-11 09:05:11 +08:00
__init__.py	establish basic structure	2012-01-18 20:06:27 -08:00