Secure Socket Layer (SSL) is a security protocol that provides a secure channel over the insecure Internet when the web browser connects to the web server. An SSL certificate is a digitally signed certificate by a certificate authority that allows the web browser to have a secure communication with the web server. This document explains the management of an SSL certificate on the WAP121 and WAP321 access points.
• WAP121
• WAP321
• 1.0.3.4
Note: For Supplicant Configuration, go through the article Configuration of 802.1X Authentication on the Cisco WAP121 and WAP321 Access Points.
Step 1. Log in to the web configuration utility and choose System Security > 802.1X Supplicant. The 802.1X Supplicant page opens:
The Certificate File Status area displays whether a certificate file exists or not.
• Certificate File Present — Indicates whether the HTTP SSL certificate file is present or not. The default is no.
• Certificate Expiration Date — Displays the expiration date of the HTTP SSL certificate.
Step 2. Click on the appropriate radio button for the appropriate file upload method in the Transfer Method field under the Certificate File Upload area.
• HTTP — The HTTP method uses the web browser to provide the certificate. Click Browse to choose the file from the local computer. Certificates with a .pem (Privacy Enhanced Mail Security Certificate) extension are only accepted.
• TFTP — The TFTP method uses a TFTP server to upload the certificate file with a .pem (Privacy Enhanced Mail Security Certificate) extension. Enter the file name of the certificate in the Filename field and the TFTP server address in the TFTP Server IPv4 Address field. Certificates with a .pem (Privacy Enhanced Mail Security Certificate) extension only accepted.
Note: A TFTP server must be installed on your computer before you proceed with TFTP transfer method. The most popular TFTP server, TFTPd32 or TFTPd64 can be downloaded here.
Step 3. Click Upload to upload the certificate file.
Step 4. Click OK to complete the upload process.
Step 5. Click Save to save the changes.
Revision | Publish Date | Comments |
---|---|---|
1.0 |
11-Dec-2018 |
Initial Release |