Yes, existing users will have to configure the hardware token again.
As the new WebAuthn APIs are not fully backward compatible with the U2F APIs implementation done in our plugin, all your users who are currently using U2F Hardware tokens (i.e. they have configured their U2F Security Keys in our 2FA plugin), will have to configure it again.
This will be a one-time configuration and we will make sure to make the reconfiguration steps as easy as possible.
After you update the plugin. The existing users will have 2 options.
Continuing using the 2FA verification using U2F APIs. They can use this option till Feb 2022 (till Chrome supports U2F)
Reconfigure the 2FA and start using the WebAuthn APIs. This option is recommended. Please note that this is a one-time process. After reconfiguration, WebAuthn will be marked as the default for those users and the 2FA verification process will be the same as before.
All these details will be mentioned in the reconfiguration flow in the plugin so that the end-users don’t get confused.