How to configure Cisco Webex Connect IM Client with IronPort Transparent HTTP/HTTPS Proxy?
Some of our users use Cisco Webex Connect, which looks like AOL IM rebranded. We can make it work for a short period of time by setting the Connection Settings as follows, but it will stop working and require us to resave the proxy settings to get it to work again.
[Checked] Connect using proxy
Username:(Blank as we don't require proxy auth)
Password: (Blank as we don't require proxy auth)
If I try it via HTTPS, it fails completely as I suspect it is not compatible with the Ironport HTTPS Proxy mode.
Thanks, Ken. I do have the Webex Application Scanning Bypass setting enabled already. I agree it is unable to work via HTTPS due to the proprietary protocol the client is using. It does seem to work sometimes, but isn't reliable. I will research the logs, as you suggested.
PS. Here is are the screenshots of the application.
Application Protection, Availability & Security
Join our webinar May 6th to gain valuable industry insights into the most recent application cyber attacks and to understand the potential impact bot traffic is having on your business.
The purpose of this document is to demonstrate how ISE authenticate / authorize a user that uses a smart card (PIN + Certificate) and password mechanism to login their system. This document describes the components used for this setup, configuration of IS...
For all versions of the Email Security Appliance (ESA) and Security Management Appliance (SMA), some Secure Sockets Link (SSL) certificates issued from the QuoVadis root certificate authority (CA) trust chain before 2021-03-31 cannot b...
Automation and programmability for networking and security are increasingly important topics. Every release since ISE 1.2 has included new REST API capabilities to better automate and integrate ISE with the rest of your network, appli...