Tokens for Storing CMS Keys and Certificates
A token is a hardware or software device that performs cryptographic functions
and optionally stores public-key certificates, cryptographic keys, and data defined
by the application using the cryptographic services. Alternatively, a token can also
be considered as a device that you can use to generate and store your key pairs and
corresponding certificates.
Certificate Management System defines two types of tokens, internal and external,
for storing key pairs and certificates that belong to the Certificate Manager,
Registration Manager, Data Recovery Manager, and Online Certificate Status
Manager.
NOTE
Internal Token
An internal (software) token refers to a pair of software files, usually called
certificate database and key database, that Certificate Management System uses to
generate and store its key pairs and certificates. Certificate Management System
automatically generates these files in the file system of its host machine when you
choose to use the internal token for the first time. These files were created for you
during CMS installation if you chose to use the internal token for key-pair
generation.
In the CMS host system, the certificate database is identified by the name
cert-<instance_id>-<machine_name>-cert7.db
by the name
these files in the
Only those who have the password that protects a token can access
it. For information on changing the password that protects a token,
use the command-line utility called the Key Database Tool, which is
explained in the CMS Command-Line Tools Guide. To locate an
online version of this document, see "Where to Go for Related
Information" on page 28.
cert-<instance_id>-<machine_name>-key3.db
<server_root>/alias
Tokens for Storing CMS Keys and Certificates
; the key database is identified
directory.
Chapter 14
Managing CMS Keys and Certificates
. You can find both
431
Need help?
Do you have a question about the NETSCAPE MANAGEMENT SYSTEM 6.0 and is the answer not in the manual?