+38Apparently this feature was finally introduced 5 months ago, yay. I’ve been waiting for this for 5 years.
I’ve just tested it today, with a PKCS#12 certificate, and unfortunately it doesn’t work.
We’ve sofar been using our own C# service provider for this, and the certificate is used here on a daily basis with success. And I’ve verified the private key password.
Has anyone tried this feature (with PKCS#12) yet with success ?
Using 2024.2.3 (build 24825).
Cheers.
Best answer by lifalin2016
I reached out to the support team, and they found a solution. Thanks Debbie.
It seems that Workbench on Windows is built with two ways for handling (SSL) certificates, Windows own (Windows Secure Channel - schannel) and OpenSSL. The former fails while the latter works.
The trick is to add or edit an environment variable named CURL_SSL_BACKEND, and set it to openssl
This will tell Workbench to use the OpenSSL implementation, which works for me.
Hope this tidbit will help others that struggle with the same problem.
+38I reached out to the support team, and they found a solution. Thanks Debbie.
It seems that Workbench on Windows is built with two ways for handling (SSL) certificates, Windows own (Windows Secure Channel - schannel) and OpenSSL. The former fails while the latter works.
The trick is to add or edit an environment variable named CURL_SSL_BACKEND, and set it to openssl
This will tell Workbench to use the OpenSSL implementation, which works for me.
Hope this tidbit will help others that struggle with the same problem.
