Date of Post is 30 Sep 2021 .Postman is not giving any response when SSL is enabled while hitting a api, but showing response with disable SSL. But my question is, the TLS "authorizationError" ="CERT_HAS_EXPIRED" but "validTo:" "Dec 15 02:30:21 2021 GMT" still have date.Means still the certificate is in valid date.Thanks for the help
You use let's encrypt. Normally the certificate would have expired today, but the have an extended period of live.
Postman has not updated our internal certificate store.
I faced this error. If you are completely sure your SSL is valid, then
Update Postman to the latest version and restart Postman
Your request should work after that. If this helped you, an upvote would be appreciated
Postman didn't update their internal Let's Encrypt certificate in time to handle the expiry of the previous one.
They acknowledged it on GitHub and released a patch on October 1st, so updating your Postman client should correct the error.
Related
Is it possible to use Postman Monitors to check how many days the SSL certificate has left before it reaches its expiration date?
When creating a request in Postman it is possible to see a popup called "Network". It contains information such as TLS protocol, Cipher name, Issuer CN and most importantly Valid until.
Inspecting the pm. object in the Tests-tab and by reading through the documentation did not yield any apparent way to get this information programmatically.
Is there any trick to get the certificate in any way programmatically inside Postman? Either via another request, some variable or property that I didn't discover yet?
Can anyone shet some light on how I can debug the matching of certificates configured in Postman?
Problem:
I’m trying to connect to a REST service using a SSL client certificate. I configured it in the settings tab the same way as in set-and-view-ssl-certificates-with-postman
When checking the console I don’t see the certificate being sent and get failure:c:\projects\electron\vendor\node\deps\openssl\openssl\ssl\s3_pkt.c:1494:SSL alert number 40
Context:
Postman v 6.4.2 running on windows 10
(for security reasons some information below replaced by dummy info)
Using the same certificate/key/password I can setup a connection using openssl. (checked for validity of certificates, TSL v1.1 and v1.2 supported, no SNI issues)
The server certificate is signed by a trusted CA (I tested with both --SSL certificate verification-- on and off )
In the Postman console I dont see the certifciate being sent.
---- [console output] ----
GET https://somehost:443/somepath?someparameter=9076443&somedate=2017-02-17T00:00:00.000
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.c:659:
Request Headers:
appid:“42”
cache-control:“no-cache”
ipaddress:“192.68.1.1”
postman-token:“some-token”
role:“Applicatie”
userid:“6x9”
---- [end console output] ----
image of certificate configuration
I matched, matched and rematched the hostname
A search on the interweb did not learn me anything I did not try yet…
Questions
Is there any debug option that will show the way the certificates are matched
is there any way I can force postman to pick a configured certificate
any other ideas on how to proceed on this problem
any help appreciated
Additional info
Monitoring with wireshark shows no certificate is sent.
(Postman console did not show a certificate being sent. I assume from examples that it will log which certificates it will/does send for a given request)
snippet wireshark output
Postman app in chrome
it does work from chrome, using the chrome keystore
Using the pk12 form of the same key (original postman request uses the .cer form) imported into the chrome keystore, the requests work.
Chrome app will not do
Obvious question is: “why not keep using the chrome app”
because its depricated and we use the newer 6.x test functions not supported in version 5.x
Question posted on Postman help forum with no answer about a week ago:
OP on postman helpforum
Additional additional info
It works on newman
I had same issue when I typed path to CRT and KEY files instead of using file dialog.
Just click Choose File button instead of pasting file path when adding certificate.
If you can download postman app then there is an option under preference/certificate and under there is an option 'Client Certificate'.
You need to provide both .cert and .key file into respective section, provide host name and key password if any. Click "save". next time you send a request matching hostname , postman app will send the certificate along with the way. You can validate in console output.
I have integrated Quickbooks invoice feature on my website.
But I am facing issue of SSL Local Issuer.
Here is the error details:
Fatal error: Uncaught QuickBooksOnline\API\Exception\SdkException: [0]: cURL error during making API call. cURL Error Number:[60] with error:[SSL certificate problem: unable to get local issuer certificate]...
Could someone advise me, how to fix this issue?
Many Thanks
Did u enabled SSL for your website?(Quickbooks app will communicate with a secure site) this link will help to solve your issue :
PHP cURL error code 60
QB Library file edit link
cURL error during making API call. cURL Error Number:[60] SSL certificate prob: self signed certificate in certificate chain
Searched a lot about this. Finally, I talked to QBO support for this.
They told me that Sometimes when we install SSL certificate on the server so it conflicts with the API inbuilt certificates. And that is the reason why the API throw SSL certificate not exist error on SSL certified website.
So they suggested my best comment out the API inbuilt certificate verification syntax.
And to achieve this we just need to comment out line with verifySSL() calling. And this is in the Same file mentioned above.
But Thank you for the help on this. I really appreciate it a lot.
URL: https://pilot-payflowpro.paypal.com
Until 12 April 2017 I had no problem but as of 13 April I failed to create a secure token.
There were no changes to the code nor to the account settings (no change in password, no "allowed IP addresses, ...").
The same code using paypal production accounts still works.
Apart from the TLS 1.2 and HTTP/1.1 upgrade I don't know about any changes on the PayPal server side.
Anyone having similar problems?
After some more digging I decided to contact PayPal technical support and I eventually (after 5 weeks) got this reply:
"There was a batch a few months ago that disabled Test accounts that hadn't been in use for a while.
They can be re-enabled only from our side...
Apologies for the inconveniences."
They kindly re-enabled our accounts and all was fine again.
I have been facing this issue with the Paypal IPN since last couple of days
I had this similar problem before which got resolved with the help of the post Paypal IPN: certificate verify failed
cURL error: [60] SSL certificate problem, verify that the CA cert is OK. Details:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
it worked fine till couple of days back and suddenly started breaking the flow
I tried by setting the curl_setopt($ch, CURLOPT_SSLVERSION, 1); but it didnt helped
Any ideas what could be the possible cause ?