Managing Tokens Used By The Subsystems - Red Hat CERTIFICATE SYSTEM 7.1 - ADMINISTRATOR Administrator's Manual

Tokens for Storing CS Keys and Certificates
e.

Managing Tokens Used by the Subsystems

There are two main tasks involved in managing the tokens used by Certificate System:
• Viewing Tokens
• Changing a Token's Password
Viewing Tokens
To view a list of the tokens currently installed for a CS instance:
Log in to the CS window (see "Logging Into the CS Console" on page 239).
1.
Select the Configuration tab, and then in the right pane, select the Encryption tab.
2.
In the Map To section, check the Token drop-down list.
3.
It shows the names (as specified when the tokens were installed) of external tokens
installed for the currently selected CS instance. For information on installing external
tokens, see "External Token" on page 306.
Changing a Token's Password
The token, internal or external, that stores the key pairs and certificates for the subsystems
is protected (encrypted) by a password. To decrypt the key pairs or to gain access to them,
you must enter that password. The first time you specified this password is when you used
the token the first time, most likely during CS installation.
308 Red Hat Certificate System Administrator's Guide • September 2005
<server_root>/shared/bin/modutil -dbdir . -nocertdb -create
This creates the required security module database file (
Administration Server's configuration directory.
At the prompt, enter this command:
<server_root>/shared/bin/modutil -dbdir . -nocertdb
-add <module_name> -libfile <library_file>
specifies the path to the DLL or other library file containing the
<library_file>
implementation of the PKCS #11 interface module.
specifies the name of the PKCS #11 module (which you
<module_name>
specified in Step 1 when you installed the drivers).
) in the
secmod.db