Which protocol prompts the Wireless LAN Controller to generate its own local web administration SSL certificate for GUI access?
Click on the arrows to vote for the correct answer
A. B. C. D.B
You can protect communication with the GUI by enabling HTTPS. HTTPS protects HTTP browser sessions by using the Secure Sockets Layer (SSL) protocol.
When you enable HTTPS, the controller generates its own local web administration SSL certificate and automatically applies it to the GUI. You also have the option of downloading an externally generated certificate.
https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-0/configuration-guide/b_cg80/b_cg80_chapter_011.htmlThe correct answer is B. HTTPS.
When accessing the graphical user interface (GUI) of a Wireless LAN Controller (WLC), a user's web browser will try to establish a secure HTTPS connection with the WLC using SSL/TLS. To do this, the WLC needs a valid SSL certificate that is trusted by the user's browser.
In some cases, the WLC may not have a valid SSL certificate from a trusted certificate authority (CA) and may not be able to obtain one due to organizational or logistical reasons. In such cases, the WLC can generate its own self-signed SSL certificate for use in HTTPS connections. This certificate will not be trusted by web browsers by default and users will be prompted with a security warning when accessing the WLC GUI. However, the user can manually accept the certificate and add it to their browser's list of trusted certificates.
Therefore, the protocol that prompts the WLC to generate its own local web administration SSL certificate for GUI access is HTTPS, as it is the protocol that initiates the SSL/TLS handshake and requires a valid SSL certificate from the server. The other options (RADIUS, TACACS+, and HTTP) are not directly related to the SSL certificate generation process.