By default, the controller is shipped with a self-signed certificate used to perform the following tasks:
This certificate is associated with topologies that have a configured L3 (IP) interface.
If you continue to use the default certificate to secure the controller and internal Captive Portal page, your web browser will likely produce security warnings regarding the security risks of trusting self-signed certificates. To avoid the certificate-related web browser security warnings, you can install customized certificates on the controller.
Note
To avoid the certificate-related web browser security warnings when accessing the controller, you must also import the customized certificates into your web browser application.