Proxy Client (V24+) ignores bindAddr parameter in proxy.ini

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

Problem Description: After upgrading the Automic Proxy from Version 12 to Version 24.4.0, the Proxy Client ignores the bindAddr= parameter defined in the proxy.ini file.

On a server with multiple network interfaces (multi-homed), the customer expects the Proxy Client to bind strictly to the IP address specified in the configuration for outbound connections. However, the Proxy Agent establishes connections using the primary interface IP (e.g., x.x.x.1) despite a secondary IP (e.g., x.x.x.2) being configured in bindAddr.

Symptoms:

• bindAddr is set in proxy.ini.

• Logs show the correct IP in the "Host information" line initially, or simply acknowledge the parameter.

• Network tools (like netstat or ss) show the established connection originating from the default/primary OS interface IP, not the configured bind address.

• Firewall rules expecting traffic from the specific bindAddr IP may block the connection.

Environment

 

Product: Automic Workload Automation

Component: Proxy Agent  (Proxy Client / Proxy Server)

Version: 24.4.x (and potentially V21+)

OS: Linux / Windows

 

Cause

The Proxy Client component (defined within the Data Center and INI file) does not open a listening socket. It only initiates outbound connections to the AE Core (JCP) or Proxy Server.

1. The bindAddr parameter in the INI file is currently treated as informational data. It is sent to the AE Core solely to be displayed in the Administration perspective (AWI) user interface.

2. Because the Proxy Client does not have a "listen" socket (bind), this parameter does not force the Operating System to bind the outbound socket to a specific source IP address during connection initiation.

Resolution

This behavior is currently considered "Working as Designed" for the Proxy architecture regarding the INI parameter.

For the Proxy Server (Listening Port): If you need to force the Proxy Server side to listen on a specific IP address only, you cannot use the INI file bindAddr. Instead, you must use the command line argument for proxy-server: --serviceAddr=x.x.x.x

For the Proxy Client (Outbound Connection): Currently, the bindAddr in the INI does not control the source IP for outbound connections in the V24 Proxy. The OS routing table determines the source interface used for the outbound connection.