api: tfa: use the new 'pve-tfa-secret' format

[pve-access-control.git] / PVE / API2 / AccessControl.pm

diff --git a/PVE/API2/AccessControl.pm b/PVE/API2/AccessControl.pm
index 9d2da8daaa80e1c53528ccd611e49ecd6f436677..6d0ea82dde6594417242215318c68a95c8a1eebf 100644 (file)
--- 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,