TLS Implementation for VCM
TECHNICAL WHITE PAPER / 30
/opt/CMAgent/CFC/3.0/bin/CSI_ManageCertificateStore -e -g fingerprint
Export existing certificates and associated keys from the certificate store:
/opt/CMAgent/CFC/3.0/bin/CSI_ManageCertificateStore -e -s subject
Export all existing certificates and associated keys from the certificate store:
/opt/CMAgent/CFC/3.0/bin/CSI_ManageCertificateStore -e -a
CSI_ManageCertificateStore Output
To provide useful feedback to the user CSI_ManageCertificateStore displays information about each certificate that
the command acts upon. The displayed information is as follows:
[Action]
Certificate:
Fingerprint:
SHA1 hash fingerprint of the certificate
Common Name:
Common name of the certificate
Subject :
Subject of the certificate
CSI_ManageCertificateStore Examples
Following are just a few examples of CSI_ManageCertificateStore use with some additional explanation to give a feel
for the tool.
Example of listing certificate store contents
By default the “-l” option for listing certificates will cause all certificates in the store to be listed. This behavior can be
modified by specifying options (for example, “-g fingerprint” will always limit the action to the single matching
certificate) that narrow the requested results.
[root@localhost tmp]# CSI_ManageCertificateStore -l
Certificate:
Fingerprint: 1C564431B9B28DC4D24BB920FD98B539FF57C0C2
Common Name: testca1.VMware.com
Subject : CN = testca1.VMware.com, ST = Colorado, C = US, emailAddress =
[email protected], O = VMware, Inc., OU = Testing
Certificate:
Fingerprint: 779403A8D53B1258F3EB09E62A8D17B14CD81DC3
Common Name: Enterprise Certificate 9ACD1B00-42CF-4794-B4E8-B6BDBEC1D4B6
