TL;DR
- Bug? Cannot set CA certificate when Postman Agent running and listening on port 10533, but not connected to the internet.
- Bug? If CA certificate is set in Postman settings (for the Postman Agent), after restart it claims “The selected PEM file is not readable. Pleas check file permissions.”
I am working on a computer using a VPN and behind a company firewall that uses HTTPS-inspection based on MyCompany-RootCA. Also I am trying to connect to internal API’s with server certificates that are signed by MyCompany-RootCA certificate.
Therefore, I need the MyCompany-RootCA.pem CA certificate file set, to be used by the Postman Agent/Desktop Agent.
Now it seems that, since the Postman/Desktop Agent is missing this certificate, it cannot connect to the internet and therefore claims to be ‘Disconnected‘. If I do a GET http://localhost:10533/knockknock from within my Postman web app, I get an “ok“. So it does listen on port 10533, but is just not connected to the internet.
In Postman Settings, it won’t let me upload a CA certificate. It claims the Desktop Agent is not up and running and needs it to be up and running for installing a certificate. That sounds like a bug to me: it is up and running, listening on port 10533, so it appears that Postman is able to communicate with the agent. So it should be able to set a certificate for the agent.
And since it needs that CA certificate to be able to connect to the internet, this seems to be a Catch 22 situation here…
After I finally got the Postman/Desktop Agent connected to the internet without CA certificate (by connecting to my mobile phone hotspot and killing the VPN), I got to set the CA certificate .pem file. And the Agent was still working after reconnecting to the company’s network.
After a restart however, I had to do this all over again, due to what seems to me as another bug: it could not read the save CA certificate .pem file anymore… (Nor .cer file in pem format.)
I checked and the file wast actually saved by Postman in my Windows 11 %userprofile% under Postman/files/xxxxxxxx/MyCompany-RootCA.pem and set as “xxxxxxxx/MyCompany-RootCA.pem“ in Postman settings.
In the Postman settings I get an exclamation mark claiming:
“The selected PEM file is not readable. Please check file permissions.“
But it’s just there in plain sight and saved there by Postman itself, so permissions should certainly not be the problem.
Running on Windows 11 Enterprise 24H2, using Postman installed as app from standard Edge webbrowser.
So please fix both:
- Enable the Postman to read the set CA certificate .PEM file again on startup.
- Setting the CA certificate file from within Postman settings. At least when Agent is running and listening on port 10533 (however disconnected or not).