RealPresence Collaboration Server (RMX) 1500/2000/4000 Administrator’s Guide
23-58
Polycom, Inc.
In compliance with
UC APL
requirements,
PKI
Self-signed Certificates
are supported for the
both the
Default
Management
and
IP
Network Services
.
A mixture of
Self-signed
and
CA-signed
Certificates
is supported, however a
CA-signed
certificate will always override a
Self-signed
Certificate
.
Self-signed Certificate Creation
Self-signed Certificates
are created during:
•
Initial system start-up before any
CA-signed Certificates
have been installed.
•
IP Network Services
creation.
•
Network Services
updates that result in
Host Name
changes.
•
Daily validity checks of
Self-signed Certificates
.
•
Backup
and
Restore
of the system configuration
Self-signed Certificate
field values are automatically inserted when the certificate is created:
Table 23-18
Self-signed Certificate - Creation
Field
Value
Signature Algorithm
SHA1
Issuer / Issued To
Service Host Name
Both the
Issuer
and
Issued To
fields have the same values.
CN = host name of the service name
DC = Polycom
OU = Self Signed Certificate
O = Polycom RMX
Note:
The value of
CN
is derived from the
IP Network Service
Name
, while the values of
DC
,
OU
and
O
are hard coded.
For a full description of these fields see
RFC 5280
.
Valid from
Date of creation
Valid to
Date of cr 10 years
Subject (Common Name)
Service Host Name
Public Key
2048 bits
Summary of Contents for RealPresence 2000
Page 26: ...RealPresence Collaboration Server RMX 1500 2000 4000 Administrator s Guide xxiv Polycom Inc...
Page 842: ...RealPresence Collaboration Server RMX 1500 2000 4000 Administrator s Guide 23 60 Polycom Inc...
Page 962: ...RealPresence Collaboration Server RMX 1500 2000 4000 Administrator s Guide E 4 Polycom Inc...
Page 968: ...RealPresence Collaboration Server RMX 1500 2000 4000 Administrator s Guide F 6 Polycom Inc...
Page 1128: ...RealPresence Collaboration Server RMX 1500 2000 4000 Administrator s Guide J 18 Polycom Inc...
