RADVision Scopia TIP Gateway, Руководство по развертыванию

Страница: 58 / 77

Note
The certificate must be signed as a certificate compatible with Base-64 ASCII code.
If other components communicating with SCOPIA Management also have their own
certificates, we recommend using a common CA for all certificates for a more
efficient implementation.
Select Web Server as the certificate template when submitting a certificate request
or renewal request.
Step 11
Continue with “Uploading SCOPIA Management Certificates into SCOPIA Management” on
page 53 .
Uploading SCOPIA Management Certificates into SCOPIA Management
This procedure describes how to upload certificates that confirm the identity of SCOPIA
Management. To upload certificates that confirm the identity of other SCOPIA Solution and
third-party devices, see
“Uploading Certificates for Other Devices” on page 61 and
“Uploading Certificates for the TIP Gateway” on page 58 .
Note
Using encryption is subject to local regulation. In some countries it is restricted or limited for
usage. For more information, consult your local reseller.
In most TLS connections, SCOPIA Management requires two certificates to be uploaded: a
signed certificate identifying SCOPIA Management signed by a certification authority (CA) and
that CA’s root certificate (
Figure 6-8 on page 53 ). Each time a deployment component tries
to establish a new TLS session with SCOPIA Management, it sends its identity certificate to the
component to establish a secure connection (
Figure 6-8 on page 53 ).
Figure 6-8 Typical TLS communication with a gateway
RADVISION | Deployment Guide for SCOPIA TIP Gateway Version 8.0 Securing Your Video Network Using TLS | 53