The HTTP adapter sends an HTTP or HTTPS request to a URL and processes the response to return the web page in XML format. This adapter does not support multiple configuration nodes. However, you can configure multiple HTTP adapters within Grid Manager, each with a required configuration node and an unique adapter name.
The HTTP adapter now also supports multi-part file upload.
The HTTP adapter might use a standard HTTP proxy server for establishing outbound HTTP connections. The HTTP adapter supports basic and NT Lan Manager (NTLM) authentication for the proxy server and the target server.
- For insecure communication, the adapter supports basic and NTLM (NTLMv1 and NTLMv2) authentication for the proxy server and the target server.
- For secure communication, the adapter supports only basic authentication for the proxy server and both basic, NTLM (NTLMv1 and NTLMv2).
The HTTP adapter now supports Kerberos to securely authenticate clients prior to executing HTTP requests on a remote host. To use Kerberos authentication, the application user must obtain ticket-granting tickets from the Kerberos server.
This adapter supports the following methods for obtaining tickets from the Kerberos server.
- Using the
kinitcommand generates the Kerberos ticket-granting ticket. This ticket is used by the adapter to connect to a target enabled with Kerberos.
You run the command on the peer on which the HTTP adapter is enabled. In the HTTP adapter request, by default, you can let the authentication to be taken care of by generating tickets by using the
For more information about running the
kinitcommand, see the .
- Specifying subject credentials: You can also specify the credentials required to access the Kerberos Key Distribution Center (KDC) in the adapter request. In this method, the adapter authenticates users based on the KDC credentials.
The HTTP adapter can use the following base adapter features. For details about these features, see Base adapter features.