What would happen if the ProxySG did not use surrogate credentials to authenticate users who use transparent proxy connections?

Using surrogate credentials in a Blue Coat ProxySG when handling transparent proxy connections allows for a seamless authentication experience for users. If surrogate credentials are not implemented, users would be required to reauthenticate each time they access a new domain. This is because the ProxySG would not have a pre-existing authenticated session for the user across different domains, necessitating a fresh authentication process for each distinct request.

This requirement can create significant friction for users as it interrupts their browsing experience and can lead to frustration, particularly in environments where users access a variety of sites frequently. By using surrogate credentials, the ProxySG maintains the authentication context, allowing users to engage with multiple domains without repeated logins. This also enhances overall efficiency and user satisfaction in network access scenarios.