Open daniellwdb opened 3 years ago
Good to know, I think we should just add your workaround in the README.md
I don't really better idea for this edge case 😅
It seems like another solution could be to add strictSSL: false
to the urlSpecReq options, maybe this property could be added dynamically with a flag so that people don't have to depend on cross-env
or set the environment variable globally, I did some reading and it's also possible to pass certificate options to the request
options but I don't think it's easy to implement this because there are different kinds of certificates, .pfx
must be parsed before used but even after I did that I couldn't get it to work, maybe somebody wants to look into that in the future
Is your feature request related to a problem? Please describe. I finally set up a dotnet core API with swagger and local https using a self signed certificate. Now I tried to consume the generated
swagger.json
so I created a command:Unfortunately this results in a clear error
Describe the solution you'd like It would be nice if we can somehow trust this certificate, however I lack knowledge to get a clear idea of what this would look like.
Describe alternatives you've considered The current workaround is to set the
NODE_TLS_REJECT_UNAUTHORIZED
environment variable