[GRADLE-2234] Since 1.0-milestone-6 gradle does not respect javax.net.ssl system properties Created: 14/Apr/12  Updated: 04/Jan/13  Resolved: 19/Sep/12

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-rc-1
Fix Version/s: 1.2-rc-1

Type: Bug
Reporter: Janning Vygen Assignee: Peter Niederwieser
Resolution: Fixed Votes: 2


 Description   

The SSL Connection to our company nexus repository is secured and we need to provide a client certificate to connect to our repository via https
Our client certificate is installed on a pkcs11 token (usb stick, Feitian PKI).

With 1.0-milestone-5 we can put these lines to the gradle wrapper script ./gradlew:
DEFAULT_JVM_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 \
"

With 1.0-milestone-5 it does work in gradle, too. But not in 1.0-milestone-6 and upwards (i tested 1.0-milestone-9 and rc-1)

gradle (or whoever) asks still for the PIN of my token but when it comes to downloading it does not work.

It seems to be related to http://issues.gradle.org/browse/GRADLE-1971
as gradle switched from java.net.URL to another lib which does not respect these system properties.

For me it is a blocker, but for the majority this might be a minor bug. But i guess it will even not work if you have a keystore on your disk which is far more common maybe.

I am eager to help you on this topic. Please tell if i can send you more information or test a new release.



 Comments   
Comment by Shin [ 01/Aug/12 ]

Confirmed by me too on 1.1. I've had to fall back to milestone 5 for now.

Comment by Janning Vygen [ 17/Aug/12 ]

This bug is really annoying as it worked before and stops me from using any gradle improvements from 1.0-milestone-6 onward. is it something which will be fixed somehow?

Comment by Adam Murdoch [ 19/Aug/12 ]

Yes, it's in the queue. The fix may make it into Gradle 1.2, but is more likely going to be in Gradle 1.3.

Generated at Wed Jun 30 12:16:24 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.