Bug Report / Feature Request — USG FLEX Web UI: 2FA verification field does not accept ENTER key

Summary

Inconsistent keyboard behaviour between the login stage and the 2FA verification stage creates a daily usability and security friction point for administrators using standalone mode with 2FA enabled.

Current behaviour

Step 1 — Username/password screen: ENTER key submits the form correctly.

Step 2 — 2FA verification screen: ENTER key does not submit. Mouse click on the Verify button is mandatory.

Why this matters operationally

TOTP codes are time-limited to 30 seconds. The forced context switch from keyboard to mouse on the 2FA screen costs 2-4 seconds minimum. When a code is in its final seconds, this delay is enough to cause the code to expire before submission, requiring the administrator to wait for the next code cycle and re-enter. Multiplied across several logins per day, across multiple devices, this is a significant and entirely unnecessary friction point.

Expected behaviour

ENTER key should submit the 2FA verification form, consistent with the behaviour of the preceding username/password screen.

Fix required

Add keydown ENTER event listener to the 2FA verification input field, identical to the implementation already present on the username/password screen. This is a one-line frontend fix.

Environment

Standalone firewall mode, web UI login, 2FA enabled, any browser.

Priority justification

Administrators managing security infrastructure should not be forced to use a mouse to complete a security-critical authentication step. The inconsistency is particularly punishing in time-sensitive TOTP scenarios.