<#55 DigiCert Global Root certificate not trusted ...
# pact-ruby-standalone
g
#55 DigiCert Global Root certificate not trusted by default Issue created by bnacey Pre issue-raising checklist I have already (please mark the applicable with an
x
): ☑︎ Upgraded to the latest version of the relevant libraries ☑︎ Checked to see if the issue has already been raised ☐ Created an executable example that demonstrates the issue using either: • a Dockerfile • a fork of https://github.com/pact-foundation/pact-ruby-standalone-e2e-example • a Git repository with a Travis or Appveyor (or similar) build • a gist with all the relevant code and full instructions on how to run it Software versions • "@pact-foundation/pact": "^9.11.0" • OS: Mac OSX 10.15.5 Expected behaviour Publishing pacts to a broker using a valid certificate with a DigiCert root should be trusted. Actual behaviour Attempting to publish to the broker results in the following error:
Failed to publish node-message-consumer/node-message-provider pact due to error: OpenSSL::SSL::SSLError - SSL_connect returned=1 errno=0 state=error: certificate verify failed One or more pacts failed to be published
Steps to reproduce 1. Create pacts using any project similar to https://github.com/pact-foundation/pact-js/tree/master/examples/messages 2. Update publish.js to point to a broker using a DigiCert root certificate 3. Attempt to publish pacts to the broker Your bug will be fixed in our free time, so help us to help you, and make it as easy as possible for us to reproduce the issue. Issues that take longer to reproduce are less likely to be fixed quickly. Please provide a Dockerfile or git repository + build, with instructions on how to reproduce the issue. Relevent log files

Screen Shot 2020-07-14 at 9 18 05 PM▾

Screen Shot 2020-07-14 at 9 17 27 PM▾

Screen Shot 2020-07-14 at 9 11 37 PM▾

Please ensure you set logging to
DEBUG
and attach any relevant log files here (or link from a gist). pact-foundation/pact-ruby-standalone