Using Corporate/Internal Signed Certificates for privately hosted repository

[Shahji]

What’s the recommended way to add corporate/internally signed certificates to gradle so it can talk to privately hosted maven/nexus repository within corporate network?

One possible way I found in search is to set the options in the environment before launching gradlew.bat, like the following -

> set JAVA_OPTS=-Djavax.net.ssl.trustStore=C:\\Windows\\win.ini -Djavax.net.ssl.trustStoreType=Windows-ROOT
> gradlew.bat

which uses host machine’s trust store for authentication. This is, however, assuming that the host machines actually has valid certs already installed. Also, this solution is M$ Windows specific. How to do something similar on Unix/Linux and Mac?

[Cinderhaze (Daryl)]

You are on the right track! You can specify the equivalent to your -D argument in ~/$GRADLE_USER_HOME/gradle.properties like the following example.

systemProp.javax.net.ssl.trustStore=“/home/user/project/gradle/keystore”
systemProp.javax.net.ssl.trustStorePassword=xyzABC

Is it possible to reference other properties in gradle.properties?

We have an ivy repository that is in a https location with a self signed certificate. I was able to get a keystore working by setting the following properties in gradle.properties: systemProp.javax.net.ssl.trustStore="/home/user/project/gradle/keystore" systemProp.javax.net.ssl.trustStorePassword=xyzABC My question, is it possible to reference other properties in gradle.properties? So I could point to $rootDir instead of hardcoding the keystore location? Something like: systemProp.javax.ne…

How to pass trustStore property in gradle build script