Partners Blog Contacts

HTTPS is enabled by default with a built-in self-signed certificate intended for bootstrapping. Properly implementing HTTPS for your VidyoConnect 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 VidyoConnect for WebRTC Server is secured using one of the following methods:

  • Single Keyed Certificate – Configure and set up VidyoConnect 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 VidyoConnect for WebRTC Server FQDNs must all be covered under the same Wildcard or SAN certificate.

 

Selecting HTTPS / HTTP Mode

To select the HTTPS / HTTP mode:

  1. Log in to the Admin interface using your account.

    For more information, see Logging in to the Admin Interface.

  2. Navigate to MAINTENANCE > SECURITY.

  3. Select any of the following options from the SSL Type drop-down:

    • HTTP+HTTPS to allow both HTTP and HTTPS connections
    • HTTPS Only to disable HTTP
    • HTTPS + HTTP Redirect to redirect HTTP requests to HTTPS

    A Confirmation dialog displays.

    Selecting_HTTPS_HTTP_Mode_1.png

    HTTPS + HTTP Redirect or HTTPS Only are recommended to keep the Admin interface secure.



  4. Click Yes.

  5. Click Apply Settings for the configuration to take effect.

    You can now browse your system over HTTPS.

  6. Browse to the VidyoConnect for WebRTC Server Admin Pages to confirm that HTTPS is working properly and that the browser does not post any security errors.

    Be sure to include the HTTPS header in the URL (e.g., https://<FQDN>/admin). Verify that HTTPS displays on the left side of the address bar and that a lock icon appears. Some browsers emphasize an HTTPS session with a color like green or blue.


    You can also verify your signed certificate by displaying information for it in your web browser. See the documentation that came with your web browser for information.

    If your browser generates a root certificate error, first check that your operating system has the latest root certificates update applied.



    If you are successful browsing to your system’s Admin pages using HTTPS and you do not receive any browser errors, continue with the next procedure.
Was this article helpful?
0 out of 0 found this helpful

0 Comments

Follow
Please sign in to leave a comment.