Cisco Cisco Email Security Appliance C160 Mode D'Emploi
15-26
Cisco AsyncOS 8.0.2 for Email User Guide
Chapter 15 Data Loss Prevention
RSA Enterprise Manager
"%JAVA_HOME%/bin/java" -cp ./emcerttool.jar
com.rsa.dlp.tem.X509CertGenerator -clientservercasigned -cacn emc-cisco
-cakeystore catem-keystore -castorepass esaem -cn ironport -storepass esaem
-keystore device-store
You can also use the following additional command-line switches:
-org <value in double quotes if it contains space>
-orgunit <value in double quotes if it contains space>
-title <value in double quotes if it contains space>
-validity <number of days>
This procedure outputs the <
device-store>.p12
file to the same folder.
This .p12 file is the certificate that you will upload to the Email Security appliance.
You will also need:
•
The .pem file from this folder, to import into the custom certificate authority list on the Email
Security appliance.
Security appliance.
•
The Device Store password that you entered.
Uploading a Certificate to the Email Security Appliance
Before You Begin
Create a .p12 certificate file. You can use the procedure in
.
Procedure
Step 1
Select Network > Certificates.
Step 2
Click Add Certificate.
Step 3
Select the Import Certificate option.
Step 4
Enter the path to the certificate file on your network or local machine.
Step 5
Enter the password for the file.
Step 6
Click Next to view the certificate’s information.
Step 7
Enter a name for the certificate. The Email Security appliance assigns the common name by default.
If Enterprise Manager manages the connected Email Security appliances at the group or cluster level, all
certificates must have the same certificate name, even though the Common Name in each certificate is
specific to each machine in the cluster.
certificates must have the same certificate name, even though the Common Name in each certificate is
specific to each machine in the cluster.
Step 8
Submit and commit your changes.