VBrick dme, Руководство администратора

Страница: 111 / 219

System Configuration
DME Admin Guide 99
3. With the encoded CSR, engage a Certificate Authority (that is trusted by all browsers
within your organization – it is recommended that you use a well known CA).
4. Purchase the certificate specifically for the correct domain name for the DME (make
sure the DME has that name, and organization DNS entries). Wildcard or star
Certificates are also common – those certificates can be use on multiple servers in your
organization. There are special naming conventions, please see the requirements of your
CA.
5. Receive the certificate from the Certificate Authority and request PEM formatting.
6. If the CSR was generated on this DME, then the private key is on this machine as well
and you can continue to step 7. However, if this is a Certificate whose CSR was
generated on another machine, you will need to procure a private key. This approach is
common when dealing with wildcard/star certificates. In order for the DME to correctly
apply the Certificate, please make sure that the private key is also in the PEM. Select the
PEM Includes Key
checkbox if applicable. When selected, you will also need to complete
an additional FQDN field to name your DME.
7. Install the certificate by pasting the PEM and all contents in the
Install New Certificate
field (at the bottom of the page) and then clicking the
Verify and Install New Certificate
button.
8. Finally, verify that your certificate was installed in the
Currently Installed Certificates
window (at the top of the page). An invalid certificate will not be installed. Also, the
DME will reboot itself when the certificate is installed correctly.
Certificates provided by a certificate authority (CA) may include multiple components: a
private certificate, one or more intermediate certificates, a root certificate, and a private key.
The order of these items (for processing by the DME) must be:
•
private key
• private cert
• intermediate cert(s)
• root cert