[pve-devel] [PATCH access-control] api: tfa: use the new 'pve-tfa-secret' format
Wolfgang Bumiller
w.bumiller at proxmox.com
Mon Oct 28 12:20:39 CET 2019
Signed-off-by: Wolfgang Bumiller <w.bumiller at proxmox.com>
---
Introduces a pve-common dependency bump.
PVE/API2/AccessControl.pm | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/PVE/API2/AccessControl.pm b/PVE/API2/AccessControl.pm
index 9d2da8d..6d0ea82 100644
--- a/PVE/API2/AccessControl.pm
+++ b/PVE/API2/AccessControl.pm
@@ -509,9 +509,7 @@ __PACKAGE__->register_method ({
optional => 1,
description => 'When adding TOTP, the shared secret value.',
type => 'string',
- # This is what pve-common's PVE::OTP::oath_verify_otp accepts.
- # Should we move this to pve-common's JSONSchema as a named format?
- pattern => qr/[A-Z2-7=]{16}|[A-Fa-f0-9]{40}/,
+ format => 'pve-tfa-secret',
},
config => {
optional => 1,
--
2.20.1
More information about the pve-devel
mailing list