In This Section: |
A certificate is automatically issued by the ICA for all internally managed entities that are VPN capable. That is, after the administrator has selected IPsec VPN in the Network Security tab of the General Properties page for network objects.
The process for obtaining a certificate from an OPSEC PKI or External Check Point CA is identical.
To create a PKCS#10 Certificate Request:
The Certificate Properties window is displayed.
The nickname is only an identifier and has no bearing on the content of the certificate.
Note - The list displays only those subordinate CA's that lead directly to a trusted CA and the trusted CAs themselves. If the CA that issues the certificate is a subordinate CA that does not lead directly to a trusted CA, the subordinate CA will not appear in the list.
The Generate Certificate Properties window is displayed.
The final DN that appears in the certificate is decided by the CA administrator.
If a Subject Alternate Name extension is required in the certificate, check the Define Alternate Name check box.
Adding the object IP as Alternate name extension can be configured as a default setting by selecting in Menu > Global Properties > Advanced > Configure > Certificates and PKI properties, the options:
add_ip_alt_name_for_opsec_certs
add_ip_alt_name_for_ICA_certs
The configuration in this step is also applicable for Internal CAs.
The public key and the DN are then used to DER-encode a PKCS#10 Certificate Request.
The Certificate Request View window appears with the encoding.
The CA administrator must now complete the task of issuing the certificate. Different CAs provide different ways of doing this, such as an advanced enrollment form (as opposed to the regular form for users). The issued certificate may be delivered in various ways, for example email. After the certificate has arrived, it needs to be stored:
An externally managed CA is the ICA of another Security Management Server. The CA certificate has to be supplied and saved to disk in advance. To establish trust:
The Certificate Authority Properties window opens.
The certificate details are shown. Verify the certificate's details. Display and validate the SHA-1 and MD5 fingerprints of the CA certificate.
The CA certificate has to be supplied and saved to the disk in advance.
Note - In case of SCEP automatic enrollment, you can skip this stage and fetch the CA certificate automatically after configuring the SCEP parameters. |
The CA's Certificate must be retrieved either by downloading it using the CA options in the Certificate Authority object, or by obtaining the CA's certificate from the peer administrator in advance.
Then define the CA object according to the following steps:
The Certificate Authority Properties window opens.
Note - For entrust 5.0 and later, use CMPV1
Note - If Automatic enrollment is not selected, then enrollment will have to be performed manually.
If the CA publishes CRLs on HTTP server choose HTTP Server(s). Certificates issued by the CA must contain the CRL location in an URL in the CRL Distribution Point extension.
If the CA publishes CRL on LDAP server, choose LDAP Server(s). In this case, you must define an LDAP Account Unit as well. See the Security Management Server Administration Guide for more details about defining an LDAP object.
Make sure that CRL retrieval is checked in the General tab of the LDAP Account Unit Properties window.
Certificates issued by the CA must contain the LDAP DN on which the CRL resides in the CRL distribution point extension.
VPN reads the certificate and displays its details. Verify the certificate's details. Display and validate the SHA-1 and MD5 fingerprints of the CA certificate.
To remove the certificate: