TDIing out loud

Ramblings on the paradigm-shift that is TDI.

Monday, December 12, 2016

Importing a client certificate in order to access an https URL

When you go to make an HTTP request to a service that requires an SSL connection, you'll get an exception that your HTTP Client Connector cannot set up the secure link to the service. Unlike your browser, TDI (SDI) does not automatically import the client certificate. You have to do this yourself, and this post is about how to do this.

For this example, we'll try to access

If you enter this URL into an HTTP Client Connector and attempt a connection either by pressing the Connect and Next buttons in the Schema area of an Attribute Map, or by dropping the Connector into an AL and running it, then you will see this error:

ERROR - [HTTPClientConnector] CTGDIS810E handleException - cannot handle exception , callreply PKIX path building failed: PKIXCertPathBuilderImpl could not build a valid CertPath.; internal cause is: The certificate issued by CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US is not trusted; internal cause is: Certificate chaining error

This error is telling us that we are missing the required client certificate. An easy fix available directly in the CE is to press the Get Certificate button located to the right of the HTTP URL parameter in the Connector's Connection tab.

This handy button will request the certificate and then store it in the TDI Server's keystore (as specified in the file by the property named

Once imported, the Java VM needs a restart in order for it to use this newly acquired cert. This means that you must recycle your TDI Server before a successful connection is possible.

This is all well and good, but if you're scripting your own components then it would be better if the missing certificate could be detected and then automatically imported. Fortunately, this is very simple to do with a single line of script in TDI.

msg =, 443)

The baseurl argument is the 'https://...' address you want to access, and 443 is the default port for HTTPS. If the socket you are trying to reach includes a specific port number, then you can use this in the above call. If the request or the keystore update fail then the returned String is an error message describing this failure. If the client cert exists already in your keystore, then the message will tell you that the cert is already trusted. And if the requested certificate is successfully added to your keystore, the message will indicate this.

CTGDIS1957I Added certificate with subject:, OU=Applications, O=", Inc", L=San Francisco, ST=California, C=US.

Once TDI has been restarted then you can make secure connections to this service.


Pieter Geerts said...

cool, does this also work for ldaps://... ?

Eddie Hartman said...

It should. Away from my PC, so I'm being optimistic, Pieter :)

Ninad Tamras said...

I don't see the Get Certificate button in the Connection tab of the HTTP Client connecter..

Also, when i try to execute the script you have mentioned above, it gives exception saying com not found. I tried adding but it gives error as "Error calling method 'GetSSLCertificate()': '' is not a valid object"

I am using TDI 7.1.1

Eddie Hartman said...

Hi @Ninad. That will depend on the version your are running. If you have TDI 7.1 or 7.1.1 then I think all you need is to install the latest fixpack for that version.

Ninad Tamras said...

Thanks @Eddie.

Upgrading the TDI is not the option at this moment.

Is there an alternate way to do it in the existing TDI?

Ninad Tamras said...

I manually added the cert to the truststore jks and got it working.