Agent Client Collector (ACC-F) : Enhancing Network Proxy Support with PAC Files

[Vasantharajan N]

A critical aspect of ACC's functionality, particularly in complex enterprise environments, is its ability to communicate effectively within diverse network configurations, including those utilizing network proxy servers. Recent enhancements to the ACC framework have significantly improved this capability through the introduction of Proxy Auto-Configuration (PAC) file support.

Let's understand the PAC File Support in ACC

Prior to ACC-F version 5.0.0, configuring the ACC agent to use a proxy server primarily relied on environment variables like HTTPS_PROXY. While functional, this method could be less flexible in environments with dynamic proxy requirements or where different proxy settings were needed for various network segments or target destinations.

for example:- when the user is connected their endpoint to office network, the traffic from ACC should be through any eligible proxies. On the other hand when the user is connected from home then it should use to connect through different different proxy enabled in internet or directly to the ServiceNow instance or ICS Gateway. 

The introduction of PAC file support addresses these limitations by allowing the ACC agent to dynamically determine the appropriate proxy server based on a JavaScript file. This file, hosted on a web server, contains rules that dictate which proxy to use (or if no proxy is needed) for specific URLs or IP addresses.

Benefits of PAC File Integration

• Dynamic Proxy Resolution: (NO Hardcoded values)

  PAC files enable the ACC agent to automatically select the correct proxy server based on the destination of its network traffic, eliminating the need for manual configuration changes when network conditions or proxy requirements shift.
• Granular Control:

  Administrators can define intricate rules within the PAC file to manage proxy usage with greater precision. This allows for tailored proxy configurations for different types of traffic or specific ServiceNow instances.
• Simplified Management:

  For large-scale deployments, PAC files streamline proxy management by centralizing the configuration. Updates to proxy settings can be made in a single location (the PAC file), which agents then automatically retrieve and apply.
• Enhanced Security:

  By directing traffic through the appropriate proxy, PAC files help ensure that ACC agent communications adhere to organizational security policies and network access controls.

Where to configure for PAC File Support

To leverage PAC file support in the ACC agent (version 5.0.0 and later), the acc.yml configuration file needs to be updated with the pac-file setting, pointing to the URL of the hosted PAC file.

pac-file: http://your-company.com/example.pac

This configuration instructs the ACC agent to fetch and utilize the specified PAC file for all its network traffic, ensuring seamless communication with the ServiceNow instance and other necessary endpoints through the defined proxy infrastructure.

Take away from this article

The integration of PAC file support in the ServiceNow Agent Client Collector significantly enhances its adaptability and manageability within complex network environments. This feature provides a more robust and flexible solution for proxy configuration, empowering organizations to deploy and operate ACC agents more efficiently while maintaining adherence to network and security policies.

Refer to KB for different options available in ACC agent to route the traffic through internet proxy  : https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1943452

#ACC #ProxySupport #Pac #PacFile