Using Java-Based NTLM Support

B2B Integration 10.4 | Administering and Monitoring B2B Transactions | Integration Server Administrator's Guide | Using NTLM Authentication when Integration Server Acts as the Client | Using Java-Based NTLM Support

By default, Integration Server uses Java-based NTLM support. The Java-based NTLM support can be used on UNIX as well as Windows platforms.

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.

Java-based NTLM authentication in Integration Server has the following limitations:

Java-based NTLM authentication supports NTLMv2 only.

Java-based NTLM authentication does not support NTLMv1.

Java-based NTLM authentication can be used with HTTP and HTTPS.

Java-based NTLM authentication in Integration Server does not work with NTLM proxy servers.

When using Java-based NTLM client authentication, keep the following information in mind:

You must provide the authentication credentials explicitly. 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

For more information about setting auth type in the pub.client:http service, see webMethods Integration Server Built-In Services Reference.

The NTLM server must be configured to send the “NTLM” header and the “Negotiate” header. If Integration Server receives only the “Negotiate” header, the NTLM handshake will not take place.

Note: If you intend to use Java-based NTML authentication, make sure native NTLM is disabled. By default, Integration Server uses Java-based NTLM authentication and native NTLM is disabled. For information about disabling native NTLM support, see Deactivating Integrated Windows Authentication.