- 15 Aug 2025
- 1 読む分
- 印刷する
- 闇光
- PDF
TLS Inspection
- 更新日 15 Aug 2025
- 1 読む分
- 印刷する
- 闇光
- PDF
TLS/SSL Inspection
Introduction
This article explains how TLS/SSL inspection affects ScreenMeet Remote Support and how to configure exceptions to ensure reliable and secure operation.
Impact of TLS/SSL inspection
Certificate pinning triggers a “not secure” warning when traffic is inspected, even in trusted corporate environments.
Beam (unattended) will not connect when TLS inspection is enabled. This is by design for connection security.
Attended sessions may operate but can present false‑positive security warnings and degraded experience.
Recommended configuration
Bypass TLS/SSL inspection for ScreenMeet services.
Add an exception for all traffic to and from
*.screenmeet.com
.Apply to port 443 over TCP and UDP where applicable.
Confirm policy precedence so the bypass is evaluated before generic decrypt rules.
Beam connectivity
Beam (unattended) connections will fail if TLS inspection is active. Implement the bypass before testing Beam.
Warning example shown to users
Typical message
“The connection to the support server may not be secure because of an SSL certificate mismatch. Certificate Issuer: CN=[Your Organization’s Root CA]. Are you sure you wish to continue?”
Common tools that perform TLS/SSL inspection
Product | Reference |
---|---|
Zscaler Internet Access | |
Blue Coat ProxySG | See vendor documentation |
Cisco Umbrella | |
Palo Alto Networks NGFW | |
Fortinet FortiGate |
Action items
Add decrypt bypass for
*.screenmeet.com
in your inspection tool.Communicate the requirement to network and security teams.
Retest attended and unattended sessions after policy changes.
Verification
Start an attended session and confirm no certificate or “not secure” warnings appear.
Start a Beam (unattended) session and confirm it connects successfully.
Inspect logs on the inspection device to ensure traffic to
*.screenmeet.com
is exempt from decryption.
Additional notes
Basic functionality may work under inspection, but bypass is recommended to avoid warnings and ensure full feature compatibility.
If you must temporarily run under inspection, advise agents and users about expected warnings.
References
Conclusion
Exclude ScreenMeet domains from TLS/SSL inspection to remove false warnings, enable Beam, and ensure full feature support.