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
..
common	Fix keystone.common.wsgi to explicitly use bytes	2016-03-02 01:30:20 -05:00
functional	Fix a few spelling mistakes	2016-06-24 02:53:48 +00:00
hacking	Remove duplicated hacking rule	2017-06-28 07:48:03 +00:00
unit	Add int storage of datetime for password created/expires	2017-08-15 18:34:20 +00:00
__init__.py	Move existing tests to unit	2015-02-13 15:54:29 -06:00