I am trying to read HTTPS requests through the proxy rather than the interceptor. To my understanding, after installing OpenSSL and restarting the application, Postman should be generating its own cert, but it is not generating any.
Explorer
OpenSSL
It is very likely I am just misunderstanding how this works, but either way, I need help. Apologies if this question appears obvious.
Yentis
(Yentis)
September 14, 2021, 4:05pm
2
I had the same issue but after installing the 1.1.1 version it managed to generate a certificate.
2 Likes
Thank you for your help. Wish it made it clearer on the post. For future readers, 1.1.1L works for me: Win32/Win64 OpenSSL Installer for Windows - Shining Light Productions
Kurmavatar
(Subramanya Raj)
September 16, 2021, 5:29am
4
Itβs a known issue that is being tracked below:
opened 11:23AM - 14 Sep 21 UTC
### Is there an existing issue for this?
- [X] I have searched the existing iss⦠ues
### Describe the Issue
Attempting to capture requests and cookies but we do not see any ca-files listed under `%APPDATA%\Postman\proxy` even though the OpenSSL has been installed and verified.
### Steps To Reproduce
1) Navigate to `%APPDATA%\Postman\proxy` to find the certificate files.
![image](https://user-images.githubusercontent.com/47771757/133248077-9f63af2b-a8f4-439e-8fbd-58eb366354ed.png)
2) Install OpenSSL and verify.
![image](https://user-images.githubusercontent.com/47771757/133248148-c6032ef0-3d1f-4453-9ec2-e73c061072d1.png)
3) Reinstall the Postman app, yet the files are missing.β
### Screenshots or Videos
_No response_
### Environment Information
```markdown
- Operating System: Windows
- Platform Type: Native App
- Postman Version: v.8.11.1
- Open SSL version: v.3.x
```
### Additional Context?
Note: **Downgrading of OpenSSL to v.1.x [from here](https://slproweb.com/products/Win32OpenSSL.html) resolves the issue.**
_Filed by Product Support_
This issue is already being tracked by the team internally, this issue is to let users who are facing a similar issues be notified upon the fix.