newman icon indicating copy to clipboard operation
newman copied to clipboard

Getting self signed certificate in certificate chain error while running collection via postman API

Open 1004Manish opened this issue 5 years ago • 5 comments

Hi,

I am running following command but getting self signed certificate in certificate chain error error.

newman run https://api.getpostman.com/collections/(UID)?apikey=(API Key) --insecure --environment https://api.getpostman.com/environments/(UID)?apikey=(API Key) I have also tried to use -k, but it also gives same error

Newman version used is 4.5.4. Please help.

Other details are:

a) When collection is exported and run as json via newman, it works fine using --insecure b) From postman app disabling SSL runs the collection fine.

Thanks!

1004Manish avatar Jul 17 '20 06:07 1004Manish

@1004Manish That's odd, you are facing this issue only when fetching the collection through the API, right?

I tried reproducing this issue locally by sending a self-signed localhost request and as you can see the -k and --insecure options are working as expected.

Screenshot 2020-07-22 at 10 43 05 AM

Can you try updating the Newman to the latest version and check if that fixes your issue?

codenirvana avatar Jul 22 '20 05:07 codenirvana

@codenirvana

I upgraded newman to version 5.1.2 and still facing the same.

1004Manish avatar Jul 22 '20 14:07 1004Manish

@1004Manish i am also facing same issue. Have you found any solution for this issue.

SRKarumuri avatar May 22 '21 12:05 SRKarumuri

I have the same issue. Have you found any solution for this issue?

emilioego avatar Jun 18 '21 11:06 emilioego

Hi Good Day

Hope you are well Sorry for very late reply I am able to run my collection in my Azure pipeline without any issue. Still facing same self signed certificate error locally ( it’s may be something to deal with organization ). I am happy that I could run it from my pipeline I no need locally 🙈

Thanks Sri

On 18 Jun 2021, at 13:27, Emilio García Orellana @.***> wrote:

 I have the same issue. Have you found any solution for this issue?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

SRKarumuri avatar Jun 29 '21 11:06 SRKarumuri