Hi,
We have an internal https web service that is failing basic security tests. It employs a self-signed certificate that, to make things worse, uses the server name "server". The CA is not within our own domain.
Still, I need to pull data from that service. The original application used cURL for that and I am in the process of SAS-ifying it. cURL has the option -k that allows it to ignore security warnings about the certificates.
From the cURL man page:
-k, --insecure
(TLS) By default, every SSL connection curl makes is verified to be secure. This option allows curl to proceed and operate even for server connections otherwise considered insecure.
When I use proc HTTP, advertised as the SAS equivalent to cURL, I see no way of straightforwardly ignoring any certificate errors or warnings. And yes, I know I shouldn't. Let's not get there. It's complicated 😉
it looks my only alternative is the import of these insecure certs and adding the ghastly hostname "server" to my DNS resolution scheme. As this will be only temporarily, I am not in favor of that approach.
Does proc HTTP have an equivalent to that -k option that I have overlooked? Is there any alternative approach?
Cheers Jan.
... View more