Below are some links to the information you will need if you decide to deploy the SecureFlow Manager (filter).
Filter implementations for a number of well-known proxies are provided by and can be requested from Unblu in binary or source code form (see below). This includes: native filter (C source code package); typically used for OEM integrations with proxy providers.
Apache Reverse Proxy filter (C source code package). Uses native filter under the hood.
|F5 BIG-IP is not supported. If you already use F5 please talk to us about it.|
In addition, the following proxies feature Filter integrations provided by Unblu and / or the proxy distributor:
Unblu can be used with or without a reverse proxy but there are a number of general benefits to using a reverse proxy such as load balancing and security, and it allows you to remove the need for direct access to your servers.
The main benefit of integrating a reverse proxy, in the case of the Unblu product, is that it allows you to use the SecureFlow Manager. The SecureFlow Manager can be used inside the filter chain of a reverse proxy to inject the snippet dynamically and accommodate co-browsing-specific communication automatically.
In cases where capture and secure resources are of particular importance, the SecureFlow Manager integration is recommended. Using the SecureFlow Manager means that all resources will come from the server and that everything is uploaded by the SecureFlow Manager. See Architecture with the SecureFlow Manager. (Depending on your current setup, using the SecureFlow Manager can harden your system by reducing the 'attack surface'.)
For a complete description of all embedded co-browsing limitations see: Limitations of Embedded Co-Browsing.