Dolph Mathews 9450cd9699 Handle tokens created and quickly revoked with insufficient timestamp precision ... In the event that the revocation event is created at the exact same timestamp as the token's creation timestamp, the event's issued_before will equal the token's issued_at and will thus not be revoked (according to the current code). This is much more likely to occur when a token's issue_at timestamp is rounded to whole seconds (rather than carrying microsecond level precision), as they are with Fernet and MySQL. Change-Id: If1f5e546463f189a0b487140a620def545006c25 Closes-Bug: 1484237 Related-Bug: 1488208		2015-08-25 12:58:53 +00:00
..
admin_crud	Split the assignments controller	2015-02-10 14:34:42 +00:00
ec2	Reuse token_ref fetched in AuthContextMiddleware.	2015-07-23 10:49:12 -07:00
endpoint_filter	EndpointFilter driver doesnt inherit its interface	2015-08-14 21:00:58 +00:00
endpoint_policy	Switch keystone over to oslo_log versionutils	2015-06-10 08:31:15 -04:00
example	Merge "Standardize documentation at Service Managers"	2015-07-15 21:11:12 +00:00
federation	Stop calling deprecated assignment manager methods	2015-08-07 14:16:42 -05:00
oauth1	Use dict.items() rather than six.iteritems()	2015-08-02 09:53:45 -05:00
revoke	Handle tokens created and quickly revoked with insufficient timestamp precision	2015-08-25 12:58:53 +00:00
s3	Fix s3.core for py34	2015-07-22 20:42:01 -05:00
simple_cert	Change oslo.config to oslo_config	2015-02-09 18:10:07 -06:00
user_crud	Use oslo.log instead of incubator	2015-02-14 05:34:52 +00:00
__init__.py	establish basic structure	2012-01-18 20:06:27 -08:00