I find the certificate data by filtering for "tcp contains " and the known CN of my certificate in both network dumps, but Firefox and curl are placing the certs on different packets. * Connection #0 to host gateway01 left intactĪs Firefox is able to authenticate, I analyzed both requests with Wireshark. < Strict-Transport-Security: max-age=31536000 includeSubDomains preload < WWW-Authenticate: Basic realm="Test Platform" * Establish HTTP proxy tunnel to testserver:443 * Uses proxy env variable https_proxy = ' * Trying 10.190.224.23. The same error occurs when using the PKCS#12 version with curl like this: curl -v -cert cert.p12 -cert-type p12 -pass foobar Is there any test server supporting certificate auth? does not seem to provide that setup. What is wrong about the failing curl call? It works, so the server supports certificate authentication. I learned that Reading double-check I tried with a Firefox Browser by merging both files to a PKCS#12 format and importing that into the browser. WWW-Authenticate: Basic realm="Test Platform" The curl call looks like this: curl -v -cert cert.crt -key key.key -pass foobar From the debug log: HTTP/1.1 401 Unauthorized We like to access a webserver using client certificate authentication instead of basic authentication.Ĭertificate is a PEM cert and the key file is a separate file.
0 kommentar(er)
