Netscape Certificate Management System 6.2, Administrator'S Manual

Page: 288 / 874

The Internal Database
288 Netscape Certificate Management System Administrator’s Guide • June 2003
❍
To change the end-entity HTTPS ip address, locate this line and edit the
value of the
ip
attribute:
<LS id="eeSSL" ip="0.0.0.0" port="443" security="on"
acceptorthreads="1" blocking="no">
4.
Save your changes and close the file.
5.
Restart the CMS instance; see “Starting, Stopping, and Restarting CMS
Instances” on page 252.
The Internal Database
Each instance of CMS uses a Netscape Directory Server instance as its internal
database. When you install a CMS instance, an internal database is created for that
instance. The install program also allows you to share a directory server between
two or more instances.
You can change the internal database used by a CMS instance. This section
describes how to change that instance and how to restrict access to the internal
database.
About the Internal Database
CMS performs various certificate and key-management functions in response to
the requests it receives. These functions include the following:
• Storing and retrieving of certificate issuance requests
• Storing and retrieving of certificate records
• Storing of CRLs
• Storing of ACLs
• Storing of privileged user and role information
• Storing and retrieving of end users’ encryption private key records
CAUTION The internal database schema is preconfigured for storing CMS data
only. Do not make any changes to it or configure CMS to use any
other LDAP directory. Doing so can result in loss of data. Also, do
not use this database for any other purpose.