The simplest resolution to this situation is to disable proxying for applications that are experiencing errors when forwarding to the Barracuda Web Filter. Applications without NTLM/Kerberos support will not pass on a user?s authentication to the Barracuda Web Filter, and in turn their web traffic will be rejected without a block page. Typical symptoms include authentication prompts, cache access denied messages, and 407 errors. If you notice a particular application is not working with an upstream Barracuda Web Filter, the source of the problem may involve proxy authentication incompatibility. ![]() However, using this scheme typically requires some advanced configuration, particularly for applications that do not explicitly support NTLM/Kerberos authentication. Using Kerberos or NTLM authentication schemes allows multiple users from the same IP address to be identified for logging and policy application. Devices installed in a forward proxy configuration with NTLM or Kerberos authentication.Back to Knowledgebase How can I troubleshoot and resolve issues with proxy authentication required errors?Īpplies where all of the following applies:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |