![]() Use Wireshark’s Packet details view to analyze the frame. GET Error: write EPROTO 101057795:error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:c:\projects\electron\vendor\node\deps\openssl\openssl\ssl\s3_pkt.c:1494:SSL alert number 40 101057795:error:1409E0E5:SSL routines:ssl3_write_bytes:ssl handshake failure:c:\projects\electron\vendor\node\deps\openssl\openssl\ssl\s3_pkt. Once you’ve spotted the request, click on it. 6) Alert 61, Level Fatal, Description: Certificate Unknown // Failing here. 5) Server sends its public key with the message Server Hello, Certificate, Server Hello Done. In the Postman console I dont see the certifciate being sent. 4) Client sends the message Client Hello to the server. The server certificate is signed by a trusted CA (I tested with both -SSL certificate verification- on and off ) ![]() (checked for validity of certificates, TSL v1.1 and v1.2 supported, no SNI issues) Using the same certificate/key/password I can setup a connection using openssl. ![]() However, if you accept that certificate, even once, the browser will. (for security reasons some information replaced by dummy info) This is nuanced, however, so a novice unfamiliar with Wireshark might be tricked. When checking the console I don’t see the ceritificate being sent and get failure:c:\projects\electron\vendor\node\deps\openssl\openssl\ssl\s3_pkt.c:1494:SSL alert number 40 I configured it in the settings tab the same way as in set-and-view-ssl-certificates-with-postman ![]() I’m trying to connect to a REST service using a SSL client certificate. Can anyone shet some light on how I can debug the matching of certificates configured in Postman?
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |