When a mobile user uses the SecoClient to log in to the FW over an SSL VPN tunnel, the system displays the following alarm information:

If the authenticity of the FW's identity can be identified, the method can be used.
Issue certificates to the SecoClient and FW.
Produce two certificates and place the device certificate on the FW and the CA certificate on the host where the SecoClient resides. If the enterprise has its own certificate system, use the enterprise's certificate system to produce certificates. If the enterprise does not have any certificate system, use the XCA software to produce certificates.
When the SecoClient accesses the FW over an SSL VPN tunnel, the FW sends a device certificate to the SecoClient. As long as the CA certificate of the SecoClient can be used to verify the device certificate of the FW, the system does not generate the alarm.
If the authenticity of the FW's identity cannot be identified, the method can be used.





When generating the device certificate, select CA for Use this Certificate for signing on the Source tab, indicating that the device certificate can be verified by the CA certificate. In this way, when establishing an SSL VPN tunnel, the SecoClient can use the CA certificate to verify the validity of the device certificate of the FW. Internal name and commonName are set to the IP address of the VPN gateway that provides VPN services. In this section, Internal name and commonName are set to 1.1.1.1.




During installation, use the default values in the dialog box.
of the virtual gateway. Select Update Local Certificate from the Certificate Authentication drop-down list. 
The password is the one set during device certificate export.

If the alarm is cleared, the certificate Verifying the Configuration succeeds.