Previously, depending on the size of CONF.fernet_tokens.max_active_keys, keys
would be pruned depending on if excess_keys was a negative slice. This caused
the key repository to never actually reach CONF.fernet_tokens.max_active_keys
in the repository in some cases.
Change-Id: Icf47d6612ef0e98e876334f56c993666df081b50
Closes-Bug: 1465444
(cherry picked from commit 46f56119a0d19f0c4075aaf0dd29f2d8cf76fa54)
Reviewed: https:/ /review. openstack. org/212945 /git.openstack. org/cgit/ openstack/ keystone/ commit/ ?id=7498154ad8c 1ee24a10e8577c6 9045fd19627530
Committed: https:/
Submitter: Jenkins
Branch: stable/kilo
commit 7498154ad8c1ee2 4a10e8577c69045 fd19627530
Author: Lance Bragstad <email address hidden>
Date: Wed Jun 17 17:05:37 2015 +0000
Fix Fernet key rotation
Previously, depending on the size of CONF.fernet_ tokens. max_active_ keys, keys tokens. max_active_ keys
would be pruned depending on if excess_keys was a negative slice. This caused
the key repository to never actually reach CONF.fernet_
in the repository in some cases.
Change-Id: Icf47d6612ef0e9 8e876334f56c993 666df081b50 c4075aaf0dd29f2 d8cf76fa54)
Closes-Bug: 1465444
(cherry picked from commit 46f56119a0d19f0