Attending To An Unresponsive Server; Password Cache - Netscape MANAGEMENT SYSTEM 6.0 Installation And Setup Manual

In the right pane, check the Server Status field.
3.
If the selected instance of Certificate Management System is running, the status
will be Started. Otherwise it will be Stopped or Unknown.

Attending to an Unresponsive Server

If an error causes Certificate Management System to become unresponsive, and all
attempts to stop it from Netscape Console fail, it may be necessary to kill the server
processes manually. For this purpose, Certificate Management System provides a
command-line tool
Guide.

Password Cache

During CMS installation, the installation program creates a password cache that
Certificate Management System uses to store all the passwords required during
start up; see "Required Start-up Information" on page 307. For example, the bind
password for the internal directory/database, which you had specified during
installation, was stored in the password cache; similarly, when you configure the
Certificate Management System for LDAP publishing, the bind password you
specify gets stored in the cache.
The password cache, a file named
symmetric key, which is generated and stored in the cryptographic module. You
can find this file in the CMS configuration directory:
<server_root>/cert-<instance_id>/config
The file is protected using the token logon/single sign-on password you specify
during installation. In the cache, passwords are stored along with a name, a string
describing the usage of the password, which is used by Certificate Management
System to index into the cache. For example, the contents of the password cache
could look like this:
----- Password Cache -----
Internal LDAP Database : myIdbPwd
Internal Key Storage Token : myTokenPwd
Authentication : myPinAuthPwd
LDAP Publishing : myLdapPubPwd
, which is explained in CMS Command-Line Tools
killproc
pwcache.db
Attending to an Unresponsive Server
, is triple-DES encrypted with a
Chapter 8 Starting and Stopping CMS Instances 315