Morgan Fainberg 66a1047e8c Add int storage of datetime for password created/expires ... Due to MySQL (in some versions) not storing datetime resolution below one second, keystone occasionally ends up with weird behavior such as a New password not being valid. The password created at and expires at columns now store both datetime (for rolling upgrades) and integers. Keystone from Pike and beyond leans on the new created_at_int column and expires_at_int column. Change-Id: I2c219b4b9b353f1e2cce6088849a773196f0e443 Closes-Bug: #1702211		2017-08-15 18:34:20 +00:00
..
backends	Add int storage of datetime for password created/expires	2017-08-15 18:34:20 +00:00
id_generators	Replace six iteration methods with standard ones	2016-09-08 18:56:31 +08:00
mapping_backends	Merge "Faster id mapping lookup"	2016-11-01 00:08:36 +00:00
shadow_backends	Set the domain for federated users	2017-01-25 22:03:52 +00:00
__init__.py	Remove exposure of routers at package level	2015-12-03 15:06:56 -03:00
controllers.py	Remove log translations in keystone	2017-03-25 18:17:15 +00:00
core.py	Unset project ids for all identity backends	2017-08-10 19:35:51 +00:00
generator.py	Replace keystone.common.config with keystone.conf package	2016-06-24 17:02:15 +00:00
routers.py	Implement HEAD method for all v3 GET actions	2016-03-22 10:27:53 -07:00
schema.py	Implement better validation for resource options	2017-01-29 13:19:44 -08:00