|This document describes version 6 of Unblu. If you’re using the latest major version of Unblu, go to the documentation of the latest version.|
The SecureFlow Manager (AKA The Filter) is the component in an Unblu integrated system that is responsible for the Injection and for Forwarding Webpage Resources (images, CSS) to the collaboration server so that they can be transmitted to the agent’s browser. Custom filters may, in addition, be responsible for Proxying certain browser requests to the server.
The filter is the link between the collaboration server and the customer’s website (web or application server). Depending on the deployment scenario the filter might be part of (or even implement) a reverse proxy, fully integrated in the client’s web or application server or integrated into the customer’s website (client side filter).
The decision on when to inject what is rule based. The rules are the main configuration element of the filter. They must stay in sync with the server settings. The collaboration server provides a json-based configuration, including rules and injection advice for the filter.
Another filter responsibility is to catch resources as they fly-by and send them to the collaboration server in case a co-browsing session is active. This is only required for setups that depend on webpage resources delivered by the server. The process of uploading webpage resources is called "add-to-cache" in the server.
Similar to injections, add-to-cache operations are rule based. Again, the corresponding rules can (and should) be retrieved from the collaboration server and must stay in sync with it over time. In contrast to injection, the provided filters do not provide uploading functionality out of the box, though. Instead, they provide a means to determine when uploading is required.
Usually, proxying is the responsibility of the reverse proxy the filter is running / integrated with. Some setups have no proxies in their existing network topology and introducing one only for the purpose of enabling co-browsing may be too expensive or for other reasons not feasible. In such cases, it may be an option to implement simple proxying yourself.
The filter configuration is json-based and can be retrieved from the collaboration server using:
hostname:portof your collaboration server and
sys-unblu with your configured systemPathPrefix.