Microsoft NTLM Support

TCC supports both Microsoft’s NTLM V1 and V2 proxy server authentication schemes. Clients with network security policies leveraging only this authentication method can now install TCC within their infrastructure in compliance with their internal policy.

Things to Consider

• Technical limitations prevents password digest retrieval from the system.

• The proxy password cannot be read from the network automatically; it must be manually entered in the batch file.

• Users must keep the password in the batch file synchronized with the Windows domain password.

• All proxy passwords MUST be encrypted.

Proxy System Properties Configuration

The Microsoft NTLM proxy server authentication scheme must be configured in files located at the root of the TCC installation folder.

• Launching TCC using Windows user interface

  When running TCC on Windows, all system properties must be defined in the TaleoConnectClient.ini file.

• Launching TCC using the command line

  When running TCC using the command line, all system properties must be passed using the command line. Insert the system properties in the TaleoConnectClient.bat file for Windows or in the TaleoConnectClient.sh file for Unix/Linux.

System Properties for NTLM Proxies

The following list contains system properties you can configure for the proxy:

• -Dhttp.proxyHost=myproxyhostname

• -Dhttp.proxyPort=8080

• -Dhttp.proxyUser=username (Windows Domain User Name)

• -Dhttp.proxyPassword=encrypted password (Windows Domain Password)

• -Dhttp.proxyNTDomain=ACMEDOMAIN (Windows Domain Name)

Note: "http.proxyNTDomain" is only required for NTML proxy authentication.