This FAQ should be read in conjunction with information on deploying Web Bridge 3 as described in Cisco Meeting Server 2.9 Release Notes, or 3.0 Deployment Guides (whichever is appropriate for the software version you are using). 

Note that Web Bridge 3 requires all of its certificate definitions to use a bundle of certificates, i.e. a full chain file. This is different to the certificate implementation for Web Bridge 2.

*Version 3.0 introduces a change to the C2W connection certificate for Web Bridge 3 so that the trust store no longer needs root certificates as was the case in 2.9. This gives administrators more flexibility on which certificates are trusted. For example, if you need to use a public certificate to protect the C2W connection due to a company's internal policies, now you can still choose not to trust all the certificates signed by that public CA but trust only the client or server C2W certificate used in the other end. This is called certificate pinning.

For more information, see: Certificate Guidelines, 2.9.x Release Notes, 3.0 Deployment Guides.

Last update:

20-Aug-2020

FAQ ID:

1490