Bug: One-Time Passcode Field Stops Accepting Input After Enter Is Pressed While It Is Empty

Version Affected: 26.0 and later
Bug Number: EE-4101
Bug Status: Open - Workaround Available
Fixed in Version(s): Not yet fixed (currently planned for 26.5)

 

Overview

On the one-time passcode (OTP) entry page, if a user presses Enter while the Passcode field is empty, the field stops accepting input. Nothing the user types appears in the field, so they cannot enter or submit a passcode until the page is reloaded or the login is restarted.

 

Cause

This is a known defect (EE-4101). To stop a passcode from being submitted twice, the OTP entry page's script (MFA.js) sets a flag when Enter is pressed, and then blocks every further key press in the field. It sets that flag even when the Submit button is disabled because the field is empty. No submission happens, so the flag is never cleared and every later key press in the field is blocked.

This defect has been confirmed in 26.0 and later. It may also be present in earlier versions.

 

Resolution / Workaround

There is no fix yet. A fix is currently planned for 26.5. Until then, the user can restore the field:

1. Reload the page in the browser, or restart the login.
2. Type the passcode into the Passcode field before pressing Enter or clicking Submit.

Pressing Enter while the field is empty locks it again, and the same steps clear it.

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.