Managing Restricted Resources Without the Filter
While the unblu filter is the high path to managing protected, session-based or encrypted resources in an embedded co-browsing session, there are alternatives for at least three cases where internal resources are being utilized.
This page lists options and alternatives to manage resources without a filter. “Protected” means that resources require authentication.
|Resource Type||Availability without the filter||Availability with the filter||Workaround|
|Static & Public||Yes||Yes||Not required|
|Static & Protected||No||Yes||Possible (Case A)|
|Dynamic / Session-based & protected||No||Yes||Possible (Case B)|
|Dynamic & Public||No||Yes||Similar to case B|
Resources can be provided to agent browser through the following mechanisms:
The Bank needs to ensure that the same resources are internally available under a different, internal URL, without the need to authenticate. This is often possible for images and CSS files that are not of a confidential nature.
The unblu server can be configured to rewrite the original resources URL to an internal URL (host). The agent browser will access the resources from the internal resource as opposed to the protected external path.
For the re-writing, the unblu server provides a configuration that allows resource patterns to be automatically re-written:
Session-specific resources (images only) can be provided to the agent browser through the following mechanism:
The application (instrumented web application) needs to provide access to the relevant resource through providing it on another URL/host – either by providing an alternative path or a copy on an alternative path.
The e-banking (instrumented application) needs to feature a logic in which all session specific resources are getting a new, additional source attribute (called unbluSrcReplacement) AND the alternative internal URL.
The application has a dynamic (or session-based) image:
<img id="chartData" src="session-specific-url-to-image"/>
The application (or an internal network component) provides access to that image through an internal URL, i.e. “agent-side-url”
The application (instrumented webpage) modifies the image element as follows:
<img id="chartData" src="session-specific-url-to-image" unbluSrcReplacement="agent-side-url"/>