Polycom CX5100 - Encrypt Configuration Files

Polycom CX5100 Unified Conference Station for Microsoft Skype for Business - Administrator Guide
Polycom, Inc. 35
● UTN-USER First-Object by COMODO
● UPS Document Exchange by DST
● ValiCert Class 1 VA
● ValiCert Class 2 VA
● ValiCert Class 3 VA
● Verisign 2048 Root CA
● VeriSign Class 4 Primary CA
● Verisign Class 1 Public Primary Certification Authority
● Verisign Class 1 Public Primary Certification Authority - G2
● Verisign Class 1 Public Primary Certification Authority - G3
● Verisign Class 2 Public Primary Certification Authority
● Verisign Class 2 Public Primary Certification Authority - G2
● Verisign Class 2 Public Primary Certification Authority - G3
● Verisign Class 3 Public Primary Certification Authority
● Verisign Class 3 Public Primary Certification Authority - G2
● Verisign Class 3 Public Primary Certification Authority - G3
● Versign Class 3 Public Primary Certification Authority – G5
● Verisign Class 4 Public Primary Certification Authority - G2
● Verisign Class 4 Public Primary Certification Authority - G3
● Verisign/RSA Commercial CA
● Verisign/RSA Secure Server CA
● Windows Root Update by COMODO
Encrypt Configuration Files
The system can recognize encrypted files. Systems can download encrypted files from the provisioning
server and can encrypt files before uploading them to the provisioning server. There must be an encryption
key on the system to perform these operations. You can encrypt configuration files (excluding the master
configuration file), contact directories, and configuration override files.
You can generate your own 32 hex-digit, 128 bit key to encrypt and decrypt configuration files on a UNIX or
Linux server.
The SDK generates a random key and applies Advanced Encryption Standard (AES) 128 in Cipher Block
Chaining (CBC) mode. For example, a key can look like this:
Crypt=1;KeyDesc=companyNameKey1;Key=06a9214036b8a15b512e03d53412006;
Troubleshoot: Polycom endeavors to maintain a built-in list of the most commonly used Certificate
Authority (CA) certificates. Due to memory constraints, we cannot ensure a complete set of
certificates.
If you are using a certificate from a commercial CA not in the list above, you can submit a feature
request for Polycom to add your CA to the trusted list. At this point, you can use the custom certificate
method to load your particular CA certificate into the system. See Using Custom Certificates on
Polycom systems (Technical Bulletin 17877).