HTTP Proxy

In certain corporate networks, IT policies enforce the use of a proxy to funnel all external HTTP requests. This is an important part of the overall network security.

The Taleo Connect Client fully supports the use of an HTTP proxy both in the runtime execution script andthrough the design environment. The configuration of the HTTP proxy follows the Java standard documented at http://docs.oracle.com/javase/1.5.0/docs/guide/net/properties.html (these are the same specifications as for the 1.6 http://docs.oracle.com/javase/6/docs/technotes/guides/net/properties.html or 1.7 http://docs.oracle.com/javase/7/docs/technotes/guides/net/properties.htmlversion).

According to these specifications, the configuration of the HTTP proxy is done at the JRE level; that is the runtime environment in which the integration process is invoked. The connectivity information is passed as system properties in either the runtime execution script or the design environment initialization file.

Hence, assuming the corporate HTTP proxy is available at proxy.acme.net on port 3128, the TaleoConnectClient.bat script should be changed to add

%JAVA_HOME%\bin\java.exe

-Dhttp.proxyHost=proxy.acme.net

-Dhttp.proxyPort=3128

-Djava.endorsed.dirs=%IC_HOME%\lib\endorsed

Certain corporate HTTP proxy implementations require an explicit authentication. This information can be provided with two extra system properties as in the following example:

%JAVA_HOME%\bin\java.exe

-Dhttp.proxyHost=proxy.acme.net

-Dhttp.proxyPort=3128

-Dhttp.proxyUser=acmeuser

-Dhttp.proxyPassword=secret

-Djava.endorsed.dirs=%IC_HOME%\lib\endorsed

Please note that we also fully support the http.nonProxyHosts property as defined in the Java specifications.

If the use of an HTTP proxy is required also in the design environment, then the following lines should be added to the TaleoConnectClient.ini file:

vmargs

-Djava.endorsed.dirs=lib/endorsed

-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

-Dhttp.proxyHost=proxy.acme.net

-Dhttp.proxyPort=3128

In previous versions, the configuration of the HTTP proxy was done in the client configuration file itself. This is no longer supported in favor of the standard way described above (see the section for more details).

Certain implementations support the https.proxyHost property although it is not part of the Java standard. The Taleo Connect Client only supports http.proxyHost, which is used for all HTTP requests (HTTP or HTTPS protocol).