HTTPS is enabled by default with a built-in self-signed certificate intended for bootstrapping. Properly implementing HTTPS for your Vidyo Neo for WebRTC Server system requires you to acquire a signed, verified Secure Socket Layer (SSL) certificate. You must register a certificate with a Certificate Authority (CA) such as VeriSign, GoDaddy, etc.

An unsigned (self-issued) certificate does not provide a guarantee of security to your users and will cause their web browsers to alert them.



Your Vidyo Neo for WebRTC Server is secured using one of the following methods:

  • Single Keyed Certificate – Configure and set up Vidyo Neo for WebRTC Server using its own separate, independently keyed certificate acquired from a CA.

  • Third Party Shared Key, CSR, Certificate Bundle – Import a shared key, CSR, and certificate bundle generated via a third-party server. Microsoft Windows server uses this method. When sharing security elements (Keys, Certificates, Bundles) with third-party servers, the server and your Vidyo Neo for WebRTC Server FQDNs must all be covered under the same Wildcard or SAN certificate.
Was this article helpful?
0 out of 0 found this helpful

0 Comments

Follow
Please sign in to leave a comment.