We have an instance of SQLA running version 17.0.11.7821 which has been making HTTPS calls for a few years now without issue then today, one endpoint we connect to renewed it's certificate and ever since then we have been getting TLS errors.
We use a generic function to call the webservice
CREATE PROCEDURE "DBA"."postHttp"( in "endPoint" long varchar,in "version" long varchar,in "type" long varchar,in "headers" long varchar,in "postData" long varchar )
url '!endPoint'
set 'HTTP(EXCEPTIONS=off; !version)'
type '!type' header '!headers'
Which we call from different procedures passing the url etc as parameters.
We DON'T define a certificate and, on Windows at least, has always meant that the OS Cert Store is used to validate certificates.
Connecting using postman on the same server works fine, again using the OS Store, with no certificate errors so I know the OS Store is validating servers certificate.
I have rebooted the server in hope it might force SQL to refresh it's connection with the OS's Cert Store, but it didn't help.
How can I force SQLA to refresh it's view of the OS certificate store when validating?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.