On 4/17/19 2:28 PM, Dominik Csapak wrote: > so one can setup a new u2f key when one is already set, otherwise > showing anything at all makes no sense
this was intentional, you do not want to make it easy overwriting existing setup keys, so one need to delete the key first... A hint for that would certainly great, though.. > > Signed-off-by: Dominik Csapak <d.csa...@proxmox.com> > --- > www/manager6/dc/TFAEdit.js | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/www/manager6/dc/TFAEdit.js b/www/manager6/dc/TFAEdit.js > index c57c5339..5cda4c07 100644 > --- a/www/manager6/dc/TFAEdit.js > +++ b/www/manager6/dc/TFAEdit.js > @@ -476,7 +476,7 @@ Ext.define('PVE.window.TFAEdit', { > handler: 'startU2FRegistration', > bind: { > hidden: '{in_totp_tab}', > - disabled: '{tfa_type}' > + disabled: '{!canSetupU2F}' > } > }, > { > _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel