I've tested that client.p12 works by installing it into Firefox, there I can see info about the intermediate certs.
#Postman for chrome browser install#
I could install client.p12 into Chrome but it doesn't seem to retain the intermediate certs, when I choose View, it only shows info about client cert. Openssl pkcs12 -in client.crt -inkey client.key -certfile middle.pem -export -out client.p12 Chrome Browser Cloud Management gives IT admins the advantage of powerful and flexible management capabilities both in the cloud and on premises, at no additional cost. Both my browser and Postman used the same IP (checked with the get request).
Potentially, the issue could be related to timing out a previous request to login. Only after these steps did the login page open in my browser. I tried to install the chain in Chrome but it seems that Chrome requires pkcs12 so I split off certchain.pem into client.crt and middle.pem, then I convert everything to pkcs12 by: Sign-out from Postman Close all Postman tabs in the browser. I have a file certchain.pem that contains client cert followed by intermediate CA 2 cert then intermediate CA 1 cert, I also have client.key file. On this page, we will go through the steps involved to download and install the Postman chrome app. Self-signed root CA => intermediate CA 1 => intermediate CA 2 => client cert My next step was to try to install the certificates in Chrome, my cert structure is like this: After some research, it seems that postman does not handle certificates itself but relies on Chrome certificates instead. I need postman to connect to my server which requires client certificate. There are many alternatives to Postman for Google Chrome if you are looking for a replacement.
0 kommentar(er)
