Publishing contracts to a broker using a self-signed SSL certificate using the Gradle plugin on MacOS doesn't work #1768
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
{{ message }}
The problem I am reporting here is quite specific, so let me explain. At the core the problem case looks something like this. When running
./gradlew pactPublishon a Java build using Pact, and publishing the contract to a Pact broker which uses thehttpsprotocol with a self-signed SSL certificate, we see the following error:when run with the
--stacktraceflag I can see:To make matters more interesting, we are only seeing this error when running the Gradle build on MacOS based systems. When run on Linux based systems this error is not reproducible.
Relevant build info:
MacOS latest release
Gradle v7.4.1
Java 11.0.16.1
Pact plugin v4.3.19
At first glance I thought the problem had to do with the self-signed cert not being trusted on the MacOS platform, however that doesn't appear to be the case. I confirmed the cert is trusted in the MacOS Keychain, and I can browse to the web UI for the Pact broker without any SSL warnings. I also tried manually adding the SSL cert to the Java key store as well using
keytoolbut that didn't work either. I also tried to find options in the Gradle build config to customize the SSL certs locations for Pact or perhaps a flag to disable the SSL verification, but there also doesn't seem to be options for those (I did find some options for the Pact Provider to do this but not the Consumer). I even dug up some esoteric env vars / Gradle properties that many Java / Gradle build tools seem to support under the hood (ie:export JAVA_TOOL_OPTIONS=-Djavax.net.ssl.trustStore=/Library/Java/Home/lib/security/cacerts,export JAVA_TOOL_OPTIONS=-Djavax.net.ssl.trustStoreType=KeychainStore, and others) but to no effect.Any help you can provide would be appreciated.
The text was updated successfully, but these errors were encountered: