topic Re: Some proxied HTTP requests fail on Windows (schannel: next InitializeSecurityContext failed) in Discussions

Some proxied HTTP requests fail on Windows (schannel: next InitializeSecurityContext failed)

OmegaMonster183 — Sun, 01 Oct 2023 14:20:58 GMT

Hello, we've found that some HTTP requests (specifically to AWS S3) fail with an HTTP proxy on Windows with the error:

schannel: next InitializeSecurityContext failed: Unknown error (0x80092012)

It looks like this may be related to these curl issues:

Do you have any suggestions for how to resolve or work around this issue? This prevents HTTP requests from working properly when using JMP in common corporate proxy environments so it's important for us to resolve.

Re: Some proxied HTTP requests fail on Windows (schannel: next InitializeSecurityContext failed)

Craige_Hales — Sun, 01 Oct 2023 21:30:13 GMT

What version of JMP? If 17, this sounds like a tech support issue. (Tab, top of page.)

Suggestions for a workaround:

If you can download a copy of curl that has the patches you need, shows how to call curl with RunProgram.

If you need to use curl on a linux machine from JMP on a windows machine, these might be helpful; they are all the same idea of using plink (putty) to create a remote shell. I would not go there if you can put curl on the windows machine.

Re: Some proxied HTTP requests fail on Windows (schannel: next InitializeSecurityContext failed)

bryan_boone — Mon, 02 Oct 2023 00:55:22 GMT

schannel error are Windows are typically due to using https and self-signed certificates or certificates that cannot be checked for revocation.
HTTP Request, which uses libcurl dynamically links to WinSSPI which is the certificate "vault" for the OS. Any certificate that is installed locally cannot be verified.

curl that Craige mentions automatically turns verification off, which while it works, will defeat the use of https. That is, the connection will still be encrypted, but the certificate used to encrypt it is unverified. In short, you have to know you trust it.

HTTP Request allows you to turn secure off, using Secure(0)

Additionally,

JMP 16 introduced:

Certificates( "c:\certs\my_certificate.crt" );

which will allow you to use your own certificate file

and

Verify SSL( "false" )

which will turn certificate verification off.