Table of Contents
Advertisement
M2M Cellular Gateway
Local Certificate List
Click on the "Generate" button and fill the required information for one certificate of the gateway.
There may be multiple certificates to be used for different applications to represent the gateway.
You also can import certificates signed by other root CAs for the gateway. You may remove
unused ones by checking the Select box of those certificates and clicking on the "Delete" button.
Local Certificate Configuration
The required information to be filled for the certificate or CSR includes the name, key and subject
name. It is a certificate if the "Self‐signed" box is checked, otherwise, it is a CSR.
Self‐signed Certificate Usage Scenario
Scenario Application Timing
When the enterprise gateway owns the root CA and VPN tunneling function, it can
generate its own local certificates by being signed by itself or import any local
certificates that are signed by other external CAs. Also import the trusted certificates
for other CAs and Clients. In addition, since it has the root CA, it also can sign Certificate
Signing Requests (CSR) to form corresponding certificates for others. These certificates
can be used for two remote peers to make sure their identity during establishing a VPN
tunnel.
Scenario Description
Gateway 1 generates the root CA and a local certificate (HQCRT) signed by itself. Import
a trusted certificate (BranchCRT) –a BranchCSR certificate of Gateway 2 signed by root
CA of Gateway 1.
Index skipping is used to reserve slots for new function insertion, when required.
280
Advertisement
Table of Contents
