pve-access-control/PVE
Thomas Lamprecht 9de25de807 partially fix #2825: authkey: rotate if it was generated in the future
Can happen if the RTC is in the future during installation and first
boot, when during key generation the clock is in the future and then,
after the key was already generated, jumps back in time.

Allow a fuzz of $auth_graceperiod, which is currently 5 minutes, as
that fuzz allows some minor, not really problematic, time sync
disparity in clusters.

If an old authkey exists, meaning we rotated at least once, check it's
time too. Only rotate if it'd not be valid for any tickets in the
cluster anymore, i.e., if it difference between the current key is >
$ticket_lifetime (2 hours)..

Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
2020-07-04 18:22:51 +02:00
..
API2 api2: AccessControl: add sdn permissions.modify 2020-06-15 15:35:03 +02:00
Auth LDAP: skip anonymous bind when clientcert/key is given 2020-05-08 13:35:18 +02:00
CLI pveum: add 'tfa delete' subcommand for deleting user-TFA 2020-05-03 16:40:05 +02:00
AccessControl.pm partially fix #2825: authkey: rotate if it was generated in the future 2020-07-04 18:22:51 +02:00
Makefile API token: add (shadow) TokenConfig 2020-01-28 20:59:45 +01:00
RPCEnvironment.pm API: add 'permissions' API endpoint 2020-01-29 21:21:58 +01:00
TokenConfig.pm token: avoid undef warning if no tokens are configured 2020-04-15 17:14:01 +02:00