Instruction Manual

USER’S GUIDE
Managed Rack PDU
205
This provides an extra level of security beyond the encryption of the user name,
password, and transmitted data.
The root certificate that you install to the browser enables the browser to
authenticate the server certificate of the Rack PDU to provide additional protection
from unauthorized access.
Disadvantage:
Because the certificates do not have the digital signature of a commercial Certificate
Authority, you must load a root certificate individually into the certificate store (cache)
of each users browser. (Browser manufacturers already provide root certificates for
commercial Certificate Authorities in the certificate store within the browser, as
described in Method 3.)
Method 3: Use the Rack PDU Security Wizard to create a certificate-signing
request to be signed by the root certificate of an external Certificate Authority
and to create a server certificate.
Use the Rack PDU Security Wizard to create a
request (a .csr file) to send to a Certificate Authority. The Certificate Authority returns a
signed certificate (a .crt file) based on information you submitted in your request. You
then use the Rack PDU Security Wizard to create a server certificate (a .p15 file) that
includes the signature from the root certificate returned by the Certificate Authority.
Upload the server certificate to the Rack PDU.
Method 3 has the following advantages and disadvantages.
Advantages:
Before they are transmitted, the user name and password and all data to and from
the Rack PDU are encrypted.
You have the benefit of authentication by a Certificate Authority that already has a
signed root certificate in the certificate cache of the browser. (The CA certificates of
commercial Certificate Authorities are distributed as part of the browser software,
You can also use Method 3 if your company or agency operates its own
Certificate Authority. Use the Rack PDU Security Wizard in the same way, but
use your own Certificate Authority in place of a commercial Certificate
Authority.