- Download 325
- File Size 200 KB
- File Count 1
- Create Date December 29, 2020
- Last Updated March 14, 2022
Best Practice Recommendation:
Background: As a part of the 5.3.0 release, the HTML5 web client is available on any Recording Server that is installed with / running v5.3.0. However, administrators and users will quickly run into Cross-Origin Resource Sharing (CORS) troubles if they acquire the web client from multiple Recording Servers. Doing so would require adding every Recording Server in the deployment to the CORS whitelist, which can create issues for IT and/or support.
In order to have a more secure, scalable, and manageable experience, we strongly recommend that the Operating System of one Recording Server is configured to designate it as the Recording Server from which the web client should be accessed. This can be co-located with the Management Server, but is not necessary. The name or address of the Windows server must be resolvable on the network on which the CompleteView deployment resides. For servers on a domain, the Fully Qualified Domain Name (FQDN) may be configured on the machine and used. Otherwise, a static IP address will suffice. Once configured, we recommend that the friendly hostname or IP address is entered into the CORS Whitelist setting – and applied to all Recording Servers (this configuration allows users to pull from any Recording Server from that friendly hostname/IP address without any CORS challenges).
Download the PDF to read the full Tech Bulletin.