Troubleshooting the web authentication fallback feature on a Cisco Catalyst switch shows that clients with the 802.1X supplicant are able to authenticate, but clients without the supplicant are not able to use web authentication.
Which configuration option will correct this issue?
Click on the arrows to vote for the correct answerA. B. C. D. E.
The web authentication fallback feature on a Cisco Catalyst switch allows clients that do not support 802.1X to be authenticated using a web portal. In this scenario, clients with the 802.1X supplicant are able to authenticate successfully, but clients without the supplicant are not able to use web authentication.
To correct this issue, the configuration option that needs to be enabled is option C: switch(config-if)# webauth. This command enables the web authentication feature on the switch port, allowing clients to authenticate using the web portal if they do not support 802.1X.
Option A: switch(config)# aaa accounting auth-proxy default start-stop group radius enables accounting for authentications that use the auth-proxy feature. This is not relevant to the issue at hand.
Option B: switch(config-if)# authentication host-mode multi-auth allows multiple authentication methods to be used on a switch port, but does not specifically address web authentication fallback.
Option D: switch(config)# ip http server enables the HTTP server on the switch, which is required for the web authentication portal to function, but it does not specifically enable web authentication fallback.
Option E: switch(config-if)# authentication priority webauth dot1x sets the priority order for authentication methods on the switch port, but it does not specifically address web authentication fallback.
Therefore, option C is the correct configuration option to enable web authentication fallback on the switch port.