A lab WLAN uses local EAP on the controller. One new engineer fails, and other local users join. That engineer was never added to the local user list. What is missing?
Select an answer to reveal the explanation.
Short Explanation
You’ve confirmed that other local users can join, but this engineer was never added to the list the WLAN checks. Add the engineer to the controller’s local user list; local EAP does not forward every user to RADIUS.
Full Explanation
Local EAP on the controller authenticates users against the local user list for that WLAN. Other local users can join, but this engineer was never added, so the missing requirement is the engineer’s entry in that list. A RADIUS server is not required simply because local EAP is in use; local EAP does not forward every user to RADIUS. A hidden SSID does not add an account to the local list, and lowering the data rate cannot make a missing user succeed. Exam caveat: an engineer who is listed but enters the wrong password can show a similar authentication failure, so after adding the account, set the password the engineer will actually type. For a practical check, add the engineer, join the lab WLAN, and read the live counters after the retest. Confirm the expected result on that live client before changing anything else on the floor; a user still absent from the list should continue to fail. This verifies the local-user requirement without changing unrelated WLAN settings.