Required Certificates

RealPresence Web Suite requires the following certificates:

Table 1. Required Certificates for RealPresence Web Suite



X.509 certificate (SSL)

To establish a secure connection with a browser, the RealPresence Web Suite Services Portal or RealPresence Web Suite Experience Portal must present an X.509 certificate.

Self-signed certificate

A self-signed certificate is required to establish a secure, encrypted connection, but it does not establish trust. Most browsers allow connection anyway, but only after presenting a warning and getting confirmation from the user to proceed.

Certificate digitally signed by a third-party Certificate Authority

To establish trust, the server must present a certificate digitally signed by a third-party Certificate Authority (CA), confirming the server identity.

The CA is the one established by your organization IT department (issuing domain certificates) or a trusted commercial CA. But the clients connecting to the server must trust the digital signature. The trusted root certificates of the major commercial CAs are embedded in browsers and imported in attendees' computers, so they trust certificates signed by those CAs without any users' configuration needed.

Trusted CA-Signed Certificates

Polycom recommends using trusted CA-signed certificates for the RealPresence Web Suite portals, the RealPresence Web Suite soft clients and for all other components of the RealPresence Clariti solution, including the RealPresence Access Director system.

Without trust, some communications among hosts—such as between the portals, the RealPresence Access Director system, and the RealPresence DMA system—may fail.

The RealPresence Access Director system certificate must be signed by a trusted commercial CA, and its SAN field must include the FQDN of the RealPresence Web Suite Experience Portal.