Using NTLM Authentication when Integration Server Acts as the Client
Integration Server supports NTLM (Windows NT LAN Manager) authentication on the connection from the Integration Server to web servers that support NTLM authentication, such as Microsoft Internet Information Server (IIS). Support for NTLM authentication allows clients that are already logged into a domain to be authenticated using their existing credentials. When acting as a client, Integration Server responds to an NTLM challenge from a web server with the appropriate authentication credentials, whether Integration Server runs on Windows, UNIX, or another supported platform.
To use NTLM authentication with Integration Server 9.7 and higher, the authentication credentials have to be provided by the user explicitly. Consequently, while providing the authorization information, you must prefix the domain name followed by a backslash (\) before the username. For example, when using NTLM as the authentication type for an invocation of the pub.client:http service, you must specify a value for the user input parameter using the format: domain_name\user_name
Note: Prior to version 9.7, Integration Server could use Integrated Windows authentication as a means of authenticating its identity while establishing connections between Integration Server and web servers on an intranet only if the Integration Server was running in Windows platforms. When Integration Server is running as an NT service, it uses the local system rights for authentication when responding to an Integrated Windows authentication. If you log on as a user, Integration Server uses the credentials associated with that session when responding to an Integrated Windows authentication.