Managing and Verifying a Key and Certicate
94LS-084
T
o encrypt communication with TLS when using Remote UI, or to use TLS as the IEEE 802.1X authentication method, a
key and certicate are required In addition, depending on the communicating device, encrypted communication using
a specied certicate may be requested, thereby requiring a key and certicate.
Managing a Key and Certicate
You can prepare a key and certicate using the follo
wing methods:
Generating a Key and Certicate on the Machine
Generate the key and certicate required for TLS on the machine. You can immediately communicate where
self-signed certicates are allowed.
Generating a Key and Certicate(P
. 316)
Registering a Certicate Issued by a Certicate Authority in a Self-generated Key
When a key is generated on the machine, generate a Certicate Signing Request (CSR), have the certicate
authority issue a certicate, and then register that certicate in the key.
Generating a Key and Certicate Signing Request (CSR) and Obtaining and Registering a
Certicate(P
. 318)
Registering a Key and Certicate or CA Certicate Obtained from an Issuing Authority
Register a key and certicate obtained from an issuing authority or a CA certicate issued by a certicate
authority, without self-generating the key and certicate. You can use a digital certicate that matches the
communicating device and authentication level.
Registering a Key and Certicate or CA Certicate Obtained fr
om an Issuing Authority(P. 321)
Verifying a Certicate
You can congur
e the settings to verify the validity of a certicate that the machine receives from a certicate
authority, using the Online Certicate Status Protocol (OCSP).
Verifying a Received Certicate with OCSP(P
. 323)
Security
315