SSL options for HttpRequest
Important: The code here is sample code only and it is not officially supported by Digital.ai. If you have questions, please contact our support team.
HttpRequest, a underlying base class for HTTP requests which is used in webhooks and is available in custom tasks.
HttpRequest is based on Apache HTTP Components.
The Apache HC default SSL configuration aims for security, however, hostname mismatches between a target host and its certificate can occur.
The following is an example of how to configure the Apache HC client in
HttpRequest with different SSL options. These examples are based on a fresh installation of Release that has SSL has enabled, and a self-signed certificate for
localhost has been generated.
From Release version 10.0.2 if you want to disable the certificate handshake, just pass
req = HttpRequest(server, verify=False)
- Create the following directory, if it does not already exist:
- Extract the
XL_RELEASE_SERVER_HOME/lib/server-<version>.jarinto the directory. This will override the
HttpRequest.pyclass provided in the JAR file. You can do this by copying the JAR file to a temporary directory, opening it with a ZIP file browser, changing the file extension to
.zipif necessary, and extracting the file from the
Create a simple sandbox release template with a single script task to test the various settings:
This fails on two counts, as expected: first, it is a self-signed certificate and, secondly, the certificate is for
nb-aphillips, which is the machine’s hostname:
HttpRequest to trust the self-signed certificate. This means changing
HttpRequest to not use the Apache HC default
HttpClient object, but one that is configured with the required SSL options.
In this example, the original
client = HttpClients.createDefault() call is commented out and a
createHttpClient method that returns a client configured to trust all certificates has been added. An additional import statement for the required classes to the initial section of
HttpRequest.py has also been added.
from org.apache.http.conn.ssl import SSLContextBuilder, SSLConnectionSocketFactory, TrustSelfSignedStrategy ... def executeRequest(self, request): client = None response = None try: # replace the original default client with a call to our new method #client = HttpClients.createDefault() client = self.createHttpClient() ... # we're adding this method to the class def createHttpClient(self): # see the Javadoc for SSLConnectionSocketFactory for more options builder = SSLContextBuilder() builder.loadTrustMaterial(None, TrustSelfSignedStrategy()) socketfactory = SSLConnectionSocketFactory(builder.build()) # print 'DEBUG: Created custom HttpClient to trust all certs\n' return HttpClients.custom().setSSLSocketFactory(socketfactory).build()
Configure the HTTP client to ignore hostname mismatches by adding an additional configuration option in the new
def createHttpClient(self): builder = SSLContextBuilder() builder.loadTrustMaterial(None, TrustSelfSignedStrategy()) # now also adding ALLOW_ALL_HOSTNAME_VERIFIER here socketfactory = SSLConnectionSocketFactory(builder.build(), SSLConnectionSocketFactory.ALLOW_ALL_HOSTNAME_VERIFIER) # print 'DEBUG: Created custom HttpClient to trust all certs and allow hostname mismatches\n' return HttpClients.custom().setSSLSocketFactory(socketfactory).build()
Additionally, can also configure the client to ignore hostnames but not to ignore trust self-signed certificates:
def createHttpClient(self): socketfactory = SSLConnectionSocketFactory(SSLContextBuilder().build(), SSLConnectionSocketFactory.ALLOW_ALL_HOSTNAME_VERIFIER) # print 'DEBUG: Created custom HttpClient to allow hostname mismatches\n' return HttpClients.custom().setSSLSocketFactory(socketfactory).build()
Note: If you configure the client to ignore hostnames but not trust self-signed certificates. Remove
TrustSelfSignedStrategy from the
org.apache.http.conn.ssl import ... line, as it is not used.
The test task will now call the server successfully:
Code samples are based on this Stack Overflow post.
Note: Considering the POODLE SSL vulnerability, you may wish to consider to allow only TLS connections. For information ON how to construct the socket factory to achieve this, see Javadoc for