From 49b15310ac76180eb25755ead90fdef871848900 Mon Sep 17 00:00:00 2001 From: Thomas Lamprecht Date: Wed, 3 Apr 2019 13:34:23 +0200 Subject: [PATCH 1/1] followup: s/CUSTOM_TFA_TYPES/USER_CONTROLLED_TFA_TYPES/ Signed-off-by: Thomas Lamprecht --- PVE/AccessControl.pm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/PVE/AccessControl.pm b/PVE/AccessControl.pm index 0c59334..af1bd6a 100644 --- a/PVE/AccessControl.pm +++ b/PVE/AccessControl.pm @@ -1354,7 +1354,7 @@ sub remove_vm_from_pool { lock_user_config($delVMfromPoolFn, "pool cleanup for VM $vmid failed"); } -my $CUSTOM_TFA_TYPES = { +my $USER_CONTROLLED_TFA_TYPES = { u2f => 1, oath => 1, }; @@ -1401,7 +1401,7 @@ sub user_set_tfa { # The 'yubico' type requires yubico server settings, which have to be configured on the # realm, so this is not supported here: die "domain '$realm' does not support TFA type '$type'\n" - if defined($data) && !$CUSTOM_TFA_TYPES->{$type}; + if defined($data) && !$USER_CONTROLLED_TFA_TYPES->{$type}; } # Custom TFA entries are stored in priv/tfa.cfg as they can be more complet: u2f uses a -- 2.39.2