Network Requirements
Proxies and TLS inspection
This page is for IT teams running a web proxy or a TLS-inspecting device. The domains each rule applies to are on Domains for user devices.
Proxies and TLS inspection
Section titled “Proxies and TLS inspection”| Traffic | Proxy | TLS inspection |
|---|---|---|
| Sign-in, portal, updates, problem reports and logs from user devices | Uses the system proxy | Works if the inspecting certificate is trusted by the device |
| Connection set-up, from devices and workstations | No proxy. Allow it directly. | Works if the inspecting certificate is trusted by the device or workstation. The app uses the operating system’s trust store, so a root pushed by your management tool is honoured. |
| Session traffic | No proxy. Allow it directly. | Encrypted end to end between the device and the workstation. Cannot be inspected; an inspecting device that alters it stops the session. |
Workstation traffic to updates.computle.com, ca-ths-1.prod.computle.com, *.id.computle.net, asmgr.computle.com and logs.svc.broker.computle.com | No proxy | Must be excluded from inspection. The workstation authenticates with its own certificate, and an inspecting proxy cannot present it. |
On the workstation, nothing uses the system proxy. The host authenticates to several services with its own certificate, so those connections cannot pass through an inspecting proxy.