Self-Signed Certificate; Self-Signed Certificate Creation - Polycom 1500 Administrator's Manual

Realpresence collaboration server
Hide thumbs Also See for 1500:
Table of Contents

Advertisement

RealPresence Collaboration Server (RMX) 1500/1800/2000/4000 Administrator's Guide

Self-signed Certificate

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:
Self-signed Certificate Field Values - Creation
Field
Signature Algorithm
Issuer / Issued To
Valid from
Valid to
Subject (Common Name)
Public Key
Polycom®, Inc.
Value
SHA1
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 MCU
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.
Date of creation
Date of creation + 10 years
Service Host Name
2048 bits
813

Hide quick links:

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the 1500 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Table of Contents