You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the form passphrase field does not validate the length of the input when a WiFi network’s security is enabled. This can lead to issues when attempting to connect to a secure network with a passphrase that does not meet the required length.
Specifically, when a user enters a passphrase of incorrect length, the Access Point (AP) disconnects and attempts to connect to the WiFi network with the user-entered credentials. If the passphrase length does not meet the requirement, the connection fails. The AP is then created again, requiring the user to reconnect. This creates a poor user experience and delays the configuration process.
For instance, in WPA/WPA2 Personal networks, each wireless network device encrypts the network traffic using a 256-bit key. This key may be entered either as a string of 64 hexadecimal digits, or as a passphrase of 8 to 63 printable ASCII characters.
To improve the user experience and prevent potential connection issues, I propose adding validation to the passphrase field. This validation should check if the entered passphrase meets the length requirements for the selected WiFi network’s security protocol before attempting to connect.
The text was updated successfully, but these errors were encountered:
thienandangthanh
changed the title
Feature Request: Password Field Validation in Web UI
Feature Request: Passphrase Field Validation in Web UI
Nov 7, 2023
Currently, the form passphrase field does not validate the length of the input when a WiFi network’s security is enabled. This can lead to issues when attempting to connect to a secure network with a passphrase that does not meet the required length.
Specifically, when a user enters a passphrase of incorrect length, the Access Point (AP) disconnects and attempts to connect to the WiFi network with the user-entered credentials. If the passphrase length does not meet the requirement, the connection fails. The AP is then created again, requiring the user to reconnect. This creates a poor user experience and delays the configuration process.
For instance, in WPA/WPA2 Personal networks, each wireless network device encrypts the network traffic using a 256-bit key. This key may be entered either as a string of 64 hexadecimal digits, or as a passphrase of 8 to 63 printable ASCII characters.
To improve the user experience and prevent potential connection issues, I propose adding validation to the passphrase field. This validation should check if the entered passphrase meets the length requirements for the selected WiFi network’s security protocol before attempting to connect.
The text was updated successfully, but these errors were encountered: