[ 
https://jira.codehaus.org/browse/WAGON-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318177#comment-318177
 ] 

Oleg Kalnichevski edited comment on WAGON-372 at 1/28/13 8:46 AM:
------------------------------------------------------------------

---
oleg@ubuntu:~/src/apache.org/maven/maven-wagon$ mvn -version
Maven home: /opt/maven
Java version: 1.6.0_35, vendor: Sun Microsystems Inc.
Java home: /opt/oracle-jdk-1.6.0.35/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.5.0-22-generic", arch: "amd64", family: "unix"
---


Oleg
                
      was (Author: olegk):
    {{{
oleg@ubuntu:~/src/apache.org/maven/maven-wagon$ mvn -version
Maven home: /opt/maven
Java version: 1.6.0_35, vendor: Sun Microsystems Inc.
Java home: /opt/oracle-jdk-1.6.0.35/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.5.0-22-generic", arch: "amd64", family: "unix"
}}}


Oleg
                  
> SSL client-side certificates stopped working in maven 3.0.4
> -----------------------------------------------------------
>
>                 Key: WAGON-372
>                 URL: https://jira.codehaus.org/browse/WAGON-372
>             Project: Maven Wagon
>          Issue Type: Bug
>          Components: wagon-http
>    Affects Versions: 2.2
>         Environment: Fedora, Ubuntu
>            Reporter: Igor von Nyssen
>         Attachments: maven-httpwagen-httpclient-ssl-setup.patch
>
>
> The following command works perfectly in Maven 3.0.3, but 3.0.4 does not seem 
> to open the key store and therefore client side certificate authentication 
> fails as maven never presents a certificate to the server.
> mvn deploy -Djavax.net.ssl.keyStore=/home/<user>/ssl/key.p12 
> -Djavax.net.ssl.keyStorePassword=****** -Djavax.net.ssl.keyStoreType=pkcs12
> adding -Djavax.net.debug=all reveals that the keystore is never loaded. 
> Confirmed with strace that the keystore file is never touched or opened.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to