|
|
|
|
|
|
|
|
iPrism networks can be configured to take advantage of both Transparent-Mode and Proxy-Mode traffic filtering. Typically, Proxy-Mode is being implemented selectively to provide filtering behavior not otherwise available. Listed below are some known scenarios.
Note: A Proxy-Mode installation cannot support Bridge-Mode, i.e., Transparent-Mode traffic. However, an iPrism Bridge-Mode installation will support both Transparent-Mode and Proxy-Mode traffic.
A Mixed-Mode iPrism environment can support requirements such as:
A mixed protocol environment, like Transparent-Mode for http web traffic & Proxy-Mode for https traffic, see:
Using iPrism Proxy-Mode for HTTPS traffic only
A mixed user environment, where you need granular profiling/reporting for Terminal Server users, in an otherwise bridged environment, see:
Citrix/Terminal Server with Windows-Authentication/AutoLogin
A mixed machine environment, like "Mac/OSX" and "Unix/Linux" clients that cannot do Transparent-Mode Auto-Login (requiring Windows clients for Windows authentication). In this case, add individual machines or groups of non-Windows machines as "Networks" and enable them for Proxy-Mode, remembering to configure iPrism in client browsers.
A mixed authentication environment (IP-Mapped vs. Session) where you want some users to have the benefits of HTTP (cached username and timeouts), but other users to login to each session explicitly. For example, in a school, you might consider the following:
Students get Proxy-Mode, using Basic Authentication, without Auto-Login
Faculty get Transparent-Mode, HTTP Authentication, with Auto-Login
