Configuring Entity Name Space - 3Com 3C13636 Configuration Manual

3Com Router 3000 Ethernet Family
Configuration Guide
configured by using the command described here, the router rejects the root certificate.
The fingerprint can be MD5 or SHA1 format.
Perform the following configuration in PKI domain view.
Table 9-7 Configure the fingerprint for authenticating the root certificate
Configure
authenticating the root certificate
Delete the fingerprint for authenticating
the root certificate
By default, no fingerprint is configured for authenticating the root certificate.
For an MD5 fingerprint, the value of the string argument must consist of 32 characters
and be entered in hexadecimal format. For an SHA1 fingerprint, the value of the string
argument must consist of 40 characters and be entered in hexadecimal format.

9.2.5 Configuring Entity Name Space

I. Name space overview
Entity name space should be taken into account when setting up PKI. In a certificate,
the public key and owner name must be consistent. Each CA details about an entity
with the information it considers important. A unique identifier (also called
DN-distinguished name) can be used to identify an entity. It consists of several parts,
such as user common name, organization, country and owner name. It must be unique
among the network.
The entity DN configuration in PKI entity view comprises the configuration of:
PKI entity name
Entity FQDN
Country code
State name
Geographic locality
Organization name
Organization unit name
Common name of the entity
IP address of the entity
Operation
the fingerprint
3Com Corporation
9-7
Chapter 9 PKI Configuration
Command
for root-certificate fingerprint { md5 |
sha1 } string
undo root-certificate fingerprint