Using Native NTLM Support via Integrated Windows Authentication
If Integration Server runs on Windows, Integration Server can use the “native” NTLM support which uses Integrated Windows authentication as a means of authenticating Integration Server’s identity. Integrated Windows authentication authenticates a user without requiring the transmission of actual passwords or sensitive account information across the network.
Which credentials Integration Server uses when responding to an Integrated Windows authentication request depends on whether Integration Server runs as a standalone application or as an NT service:
If
Integration Server runs as a standalone application, it uses the credentials of the logged in Windows user.
If
Integration Server runs as an NT service, it uses the local system rights for authentication. If you log on as a user,
Integration Server uses the credentials associated with that session when responding to an Integrated Windows authentication
Native NTLM authentication in Integration Server has the following limitations:
Native NTLM authentication is for Windows systems only.
Native NTML authentication supports HTTP only.
Native NTLM authentication is not supported for NTLM proxy servers.
For
Integration Server to use native NTLM support the web server must support Integrated Windows authentication. Microsoft Internet Information Server (IIS) is an example of a web server that supports Integrated Windows authentication.
To use native NTML authentication on
Integration Server, you must first activate Integrated Windows authentication on
Integration Server. For information about activating Integrated Windows authentication, see
Activating Integrated Windows Authentication.