iTP Secure WebServer System Administrators Guide (Version 7.5+)

Table 3 Example Default Root Certificate (continued)
C: US
State: Root Enabled
Private Key: Not Present
Public Key: Present
Certificate: Present
-----------------------------------
Distinguished Name
OU: Directory Services
O: AT&T
C: US
State: Root Enabled
Private Key: Not Present
Public Key: Present
Certificate: Present
-----------------------------------
Distinguished Name
OU: Transaction Services
O: AT&T
C: US
State: Root Enabled
Private Key: Not Present
Public Key: Present
Certificate: Present
-----------------------------------
Distinguished Name
CN: GTE CyberTrust Root
O: GTE Corporation
C: US
State: Root Enabled
Private Key: Not Present
Public Key: Present
Certificate: Present
-----------------------------------
Distinguished Name
CN: Open Market, Inc.
OU: No Assurance Beta Certificates
OU: For testing and evaluation use only
O: OMI Persona CA
L: Cambridge
ST: MA
C: US
State: Root Enabled
Private Key: Not Present
Public Key: Present
Certificate: Present
-----------------------------------
You can use the keyadmin utility's -initdefaults option to update the default root certificates
in your key database file. This option causes:
• Existing root certificates to be updated in those cases where keyadmin has more recent
information
• Root certificates not found in the database to be added
To update the default root certificates in the database, use this keyadmin command:
keyadmin -keydb keydb -initdefaults [-verbose]
The command arguments have these functions:
-keydb keydb
specifies the name of the key database file in which the key pair you created is
stored.
-initdefaults
specifies that you want to update the default root certificates in your key database
file.
66 Configuring for Secure Transport