If your organization uses an outgoing proxy server to connect to the Internet, the Secure Agent connects to Informatica®Intelligent Data Management Cloud™ (IDMC) through the proxy server.
You can configure the Secure Agent to use the proxy server on Windows and Linux. You can use the unauthenticated or authenticated proxy server.
Note:
You cannot use a proxy server with managed identity authentication.
You can use one of the following types of proxy servers:
•Unauthenticated proxy - Requires only the host and port address for configuration.
•Authenticated proxy - Requires the host address, port address, user name, and password for configuration.
To configure proxy settings for the Secure Agent, use one of the following methods:
•Configure the Secure Agent through the Secure Agent Manager on Windows or shell command on Linux.
For instructions, see "Configure the proxy settings on Windows" or "Configure the proxy settings on Linux" in Getting Started in the Data Integration help.
•Configure the JVM options for the DTM in the Secure Agent properties. For instructions, see the Proxy server settings Knowledge article.
•
You can configure host patterns to bypass the configured forward proxy and connect directly to Oracle Cloud Object Storage. As a result, you can route traffic according to your network policies instead of sending every connection through the proxy.
Configure the bypass list in one of the following ways:
- In the proxy.ini file in the agentcore/conf directory, set InfaAgent.NonProxyHost to a pipe-delimited list of host patterns. Restart the Secure Agent for the change to take effect.
- In the Data Integration Server properties for the DTM, add the JVM option -Dhttp.nonProxyHosts=host1|host2. When you save the configuration, the Data Integration Server restarts.
Use an asterisk (*) as a wildcard in a host pattern. You can place the wildcard anywhere in the pattern, including in the middle. For example, use objectstorage.*.oraclecloud.com to bypass the proxy for Oracle Cloud Object Storage endpoints in every region.
The connector matches a pattern against the host name, not the resolved IP address. A pattern in CIDR notation, such as 172.16.0.0/16, doesn't bypass the proxy.