[jira] (WAGON-372) SSL client-side certificates stopped working in maven 3.0.4

["Graham Leggett (JIRA)" <ji...@codehaus.org>]

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

Graham Leggett commented on WAGON-372:
--------------------------------------

We can also confirm that client certificate support is broken in maven v3.0.4, we also see no attempt by maven to read the keystore when -Djavax.net.debug=ssl:handshake is enabled.

The workaround works, however this is a support burden for us, as every new developer that comes on board must manually configure this.

                
> 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
>
> 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