I've tested that my certs work by doing a curl with them. 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 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: 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. Long story short, it is a Chrome extension which allows you to send http requests in a very easy and intuitive. Self-signed root CA => intermediate CA 1 => intermediate CA 2 => client cert If you are doing any kind of rest api development you probably have heard of Postman. My next step was to try to install the certificates in Chrome, my cert structure is like this:
The result is a great looking web page with all the API calls, docs and sample requests and responses in one place.
After some research, it seems that postman does not handle certificates itself but relies on Chrome certificates instead. This turns Postman from a personal API utility to full-blown public interactive API documentation. 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.