Apologies for any delays here - Have you directly contacted our support team or raised an issue in our Github Issue Tracker, to alert the team of this problem?
As this is primarily the Postman Community forum, full of discussions about all things Postman, it can be difficult to see this individual topic and subsequent threads amongst all the other topics created on a daily basis.
If there is anything I can do to help out here, I’m available to do so.
For others here, we ran across this problem in our enterprise and stumbled onto the fact that the newman flag --ssl-extra-ca-certs=path/to/cert.pem appears to work for the postman cli, even though it’s not documented.
The = may not be required, depending on your specific script. Both --param=value and --param value formats worked on my end.
I’ll raise this with the team again today to try and find a solution/workaround/more information.
The Postman Community Forum is not the best or efficient place to raise issues and get them in front of the dev team, as you can see from the thread it’s all Postman users talking to each other.
As new topics get raised in the forum, others get pushed down the list and can get missed very easily.
I recommend that all issues and feature requests are raised on our GitHub Issue Tracker, the links/icons for these can be found in the header of each forum page.