Item Notes Description
Cancel Button Click the Cancel button to discard the import operation and
the screen will return to the Trusted Certificate page.
Table 126 – Trusted Client Key Import - From File & From a PEM
4.5.5 Issue Certificate
When you have a Certificate Signing Request (CSR) that needs to be certificated by the root CA of the device, you can issue
the request here and let the Root CA sign it. There are two approaches to issuing a certificate:
Import a CSR file from the managing PC and then click on the Sign button, or
Copy-paste the CSR codes into the router’s web- based utility and then click on the Sign button.
If the router signs a CSR successfully, the Signed Certificate View section will display the signed certificate’s contents.
Use the Download button to save a backup copy of the signed certificate as a file on the managing PC.
Self-signed Certificate Usage Scenario
Figure 217 – Self-signed Certificate Usage Scenario
Scenario Application Timing
(same as the one described in "My Certificate" section)
When the enterprise gateway owns the root CA and VPN tunnelling function, it can generate its own local certificates by self-
signing them. It also imports the trusted certificates for other CAs and Clients. These certificates can be used for two remote
peers to verify their identity during establishment of a VPN tunnel.
Scenario Description
(same as the one described in "My Certificate" section)
Router 1 generates the root CA and a local certificate (HQCRT) signed by itself. It also imports a trusted certificate
(BranchCRT) –a BranchCSR certificate of Router 2 signed by root CA of Router 1.
To Next Page
Loading...
Need help?
General