DescriptionHow do I configure self signed certificate using controller GUI
SolutionGUI CONFIGURATION STEPS:
1. Click on Configuration>Certificate Management>Server Certificates>Click on the ADD button.
2. Under “Certificate Add” fill in the following fields
- Choose the radio button named “Create a Self Signed certificate”.
- Fill “Certificate Alias” text box with a name (Name can be of 1 to 31 alphanumeric characters)
- Enter the private key password (Make a note of this key).
- Enter the validity text box for which the certificate has to be valid.
3. Under Distinguished Name (DN), enter the following fields
- Common
Name - This is a Fully Qualified Domain Name (FQDN) of the controller.
The FQDN should be resolved by the wireless clients connecting to the
captive port SSID. (For ex.: The wireless clients connecting to the SSID
with captive portal should be able to resolve the FQDN of the
controller).
- Organization Unit Name
- Organization Name
- Locality Name
- State Name
- Country Code
- E-mail Address
4. Now a self signed certificate is created.
5.
Select the server certificate or highlight it and click on Export. Now
export the file with the name filename.cer to the desktop.
6. Click on Configuration>Certificate Management>Trusted Root CA and import the filename.cer file.
7. Now, the certificate is self signed on the controller. Refer the screenshot below.
8.
On the cert we could see that the certificate is “issued to” itself.
Select the certificate and click on the option “Used by” in order to
apply this certificate usage for captive portal or Web GUI.
9.
Here the “print.merulab.com” is the root certificate which is not known
to the browsers “Trusted Root Store”. So if the certificate is used by
either captive portal or the web interface there will be error stating
that the certificate is not valid. Need to save it in the certificate
store of the browser in order to avoid the errors.
