Select Export and save the file on your diskģ. Select the file you saved on your disk in step 3.Ģ. Go to the Trusted Root Certification Authorities tab and click on importĦ. Go to Chrome > Settings, search for SSL (chrome://settings/search#ssl) and click on Manage certificatesĥ.
In the dialog that comes up, click ‘View Certificate’, and drag the certificate icon to your desktop to create a *.cer file.Chrome uses the underlying OS layer to handle SSL certificates. The dialog that comes up now depends on the operating system you are on. Open the Connection tab in the dropdown that comes up.Click on the lock icon on the top left in the URL bar.Turns out that there is a better solution to solve this a problem, and it also avoids adding an exception to Chrome every time you start the browser. If you try to hit a URL with a self-signed SSL certificate, you would get a 500 error as Chrome would decline the certificate: But this doesn’t work with the new packaged app. With the legacy app, you could go to the root URL in Chrome and allow the browser to access URLs with self-signed certificates. Self-signed certificates are often used in testing and development environments to provide a layer of security for an API As they are not verified by a trusted authority, accessing an API endpoint with something like through the Postman Chrome App, would throw up an error like this:
#POSTMAN EXTENSION CHROME MAC#
If you’re using the Mac app, head to our documentation for details on ignoring SSL errors.
This post is applicable to the Postman Chrome app only. 2020 Update: If you want to dig deeper into self-signed SSL certificates, check out our related post called Troubleshooting Self-Signed SSL Certificate Issues and More in Postman.
0 kommentar(er)
