Has anybody succeed with using a pkcs#11 token to access a remote repository with gradle?


(Janning Vygen) #1

Has anybody succeed with using a pkcs#11 token to access a remote repository with gradle?

I already posted my question on stackoverflow (here: http://stackoverflow.com/questions/10067257/gradle-company-repository-needs-ssl-client-certificate). Sorry for double posting, but i don’t know if gradle guys hang around at stackoverflow.

With maven i just had to add

MAVEN_OPTS="$MAVEN_OPTS \
            -Djava.security.debug=sunpkcs11 \
     -Djavax.net.ssl.trustStore=NONE \
     -Djavax.net.ssl.trustStoreType=pkcs11 \
            -Djavax.net.ssl.keyStore=NONE \
            -Djavax.net.ssl.keyStoreType=pkcs11 \
  "

I put these vars to gradle wrapper script and it ask for my token PIN but it still can’t access the repository.

At the moment we try to migrate huge project from maven to gradle. Gradle seems to be much better…


(Janning Vygen) #2

I opened an issue as it seems to be a bug since milestone-6: http://issues.gradle.org/browse/GRADLE-2234