Table of Contents

Search

  1. Preface
  2. Runtime environments
  3. Hosted Agent
  4. Secure Agent groups
  5. Serverless runtime environments
  6. Connectors in a serverless runtime environment
  7. Secure Agents
  8. Secure Agent installation

Runtime Environments

Runtime Environments

Configuring a proxy server for the Secure Agent

Configuring a proxy server for the Secure Agent

A proxy server allows indirect connection to network services for security and performance reasons. For example, you can use a proxy server to get through a firewall, and some proxies provide caching mechanisms.
When you configure a proxy server for the Informatica Cloud Secure Agent, you define the minimum required settings in the Secure Agent Manager.
Informatica Intelligent Cloud Services
updates the following file and adds other properties that you can edit manually:
<Secure Agent installation directory>/apps/agentcore/conf/proxy.ini
The following code shows the default contents of
proxy.ini
:
InfaAgent.ProxyPassword=ZU8KjIzgtVrVmfRMUPzPMw\=\= InfaAgent.ProxyNtDomain= InfaAgent.ProxyHost=foo.bar.com InfaAgent.ProxyPasswordEncrypted=true InfaAgent.NonProxyHost=localhost|127.*|[\:\:1] InfaAgent.ProxyUser= InfaAgent.ProxyPort=12345 InfaAgent.AuthenticationOrder=
When you configure a proxy server for the Informatica Cloud Secure Agent, you can set InfaAgent.NonProxyHost to exclude certain IP addresses and host names from the proxy.
For example, when you use managed identity authentication to connect to an Azure source or target in a mapping that runs in advanced mode, exclude the IP address of the metadata service, 169.254.169.254.

0 COMMENTS

We’d like to hear from you!