Providing additionally trusted CA certificate to newman
See original GitHub issueHi there,
I am using newman 4.5.5 (and love it - great work!) on Mac, installed via brew.
In newman, there are useful options for providing SSL client certificate and key files when running a collection against a https API, that verifies client certificates. However, there is no option to privide a trusted CA certificate.
This causes issues when testing APIs, that use a self signed server certificate, that thus cannot be verified by newman.
I know, that the --insecure
option can be used to disable certificate verification, but in my opinion, this defeats the purpose - newman should be able to verify the server certificate even though it is self signed.
Is there a specific reason, why this functionality is not implemented so far? I had a quick look in the newman code and to mee, it seems, that the extra CA could be passed to the postman-runtime
in lib/run/index.js, when the runner.run()
function is called. There, the requester
options can be set. According to postman-runtime
, an extra CA can be provided here.
what do you think? Might this be feasible, or do you perfer to use the --insecure
flag?
Cheers Julian
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:5 (1 by maintainers)
--ssl-extra-ca-certs
option is added in Newman v4.6.0 🎉Hello folks, I have implemented the feature in PR #2208. Your support for this PR is much apprecated.
Cheers Julian