260
Certificate request from an RSA Keon CA server
Network requirements
The switch submits a local certificate request to the CA server. The switch acquires the CRLs for certificate
verification.
Figure 80 Network diagram
Configuring the CA server
1. Create a CA server named myca:
In this example, you need to configure these basic attributes on the CA server at first:
{ Nickname—Name of the trusted CA.
{ Subject DN—DN information of the CA, including the Common Name (CN), Organization Unit
(OU), Organization (O), and Country (C).
Use the default values for the other attributes.
2. Configure extended attributes:
After configuring the basic attributes, perform configuration on the jurisdiction configuration page
of the CA server. This includes selecting the proper extension profiles, enabling the SCEP
autovetting function, and adding the IP address list for SCEP autovetting.
3. Configure the CRL distribution behavior:
After completing the configuration, you must perform CRL related configurations. In this example,
select the local CRL distribution mode of Hypertext Transfer Protocol (HTTP) and set the HTTP URL
to http://4.4.4.133:447/myca.crl.
After the configuration, make sure the system clock of the switch is synchronous to that of the CA,
so that the switch can request certificates and retrieve CRLs properly.
Configuring the switch
1. Configure the entity name as aaa and the common name as
d
evice.
<Device> system-view
[Device] pki entity aaa
[Device-pki-entity-aaa] common-name device
[Device-pki-entity-aaa] quit
2. Configure the PKI domain:
# Create PKI domain torsa and enter its view.
[Device] pki domain torsa
# Configure the name of the trusted CA as myca.
[Device-pki-domain-torsa] ca identifier myca
# Configure the URL of the registration server in the format of http://host:port/Issuing Jurisdiction
ID, where Issuing Jurisdiction ID is a hexadecimal string generated on the CA server.
To Next Page
Loading...
Need help?
General