Authentication behavior for SOCKS traffic when both SOCKS and Web authentication layer exists

Products

• ProxySG Software - SGOS
• Advanced Secure Gateway Software - ASG

Issue/Introduction

What will be the behavior of policy outcome if the SOCKS proxy policy is set to "do not require authentication" and a Web authentication layer also exist in the policy which will match the Traffic condition?

Environment

ProxySG OS

Resolution

Processing of web authentication layer rules are after the SOCKS authentication layer as mentioned here, Policy sequence for ProxySG.

So if there is a matching policy under the Web authentication layer for ClientIP then it will not work with SOCKS traffic.

e.g. 

SOCKS authentication layer = do not authenticate for ClientIP
Web authentication layer = do not authenticate for ClientIP
result traffic will be allowed without authentication.

SOCKS authentication layer = do not authenticate for ClientIP
Web authentication layer = any IP required authentication
result traffic will not work as the SOCKS client might not be able to perform authentication with proxy.