AC-9437: 2FA U2F screens need error handling when not available

Changed error handling to show the raw WebAuthn message because the browser does not provide a consistent mechanism to differentiate between NotAllowError types. These errors can range from auth timeout to TLS errors or even just user declining the browser prompts.

Author: nathanjosiah

TwoFactorAuth/view/adminhtml/web/js/u2fkey/auth.js

@@ -162,8 +162,8 @@ define([
         _onCredentialError: function (u2fError) {
             this.idle(true);
 
-            if (['AbortError', 'NS_ERROR_ABORT', 'NotAllowedError'].indexOf(u2fError.name) === -1) {
-                error.display($t('Unable to register your device'));
+            if (['AbortError', 'NS_ERROR_ABORT'].indexOf(u2fError.name) === -1) {
+                error.display($t(u2fError.message));
             }
         }
     });

TwoFactorAuth/view/adminhtml/web/js/u2fkey/configure.js

@@ -154,8 +154,8 @@ define([
         _onCredentialError: function (u2fError) {
             this.idle(true);
 
-            if (['AbortError', 'NS_ERROR_ABORT', 'NotAllowedError'].indexOf(u2fError.name) === -1) {
-                error.display($t('Unable to register your device'));
+            if (['AbortError', 'NS_ERROR_ABORT'].indexOf(u2fError.name) === -1) {
+                error.display($t(u2fError.message));
             }
         }
     });