You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Chris Owens (JIRA)" <ji...@codehaus.org> on 2013/05/16 19:10:52 UTC

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

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

Chris Owens commented on WAGON-372:
-----------------------------------

I am still experiencing this problem with the tomcat7-maven-plugin, whose "Deploy" goal I believe uses the same underlying plumbing. 

It fails under tomcat7 plugin versions 2.0 or 2.1, under
Maven 3.0.5, with either the wagon 2.4 code that ships with maven 3.0.5, or with the lightweight 2.2 version in the comments above, and with -Dmaven.wagon.http.ssl.easy=false or true.


                
> 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
>            Assignee: Olivier Lamy
>             Fix For: 2.4
>
>         Attachments: maven-httpwagen-httpclient-ssl-setup.patch, maven-httpwagen-httpclient-ssl-setup-refactoring.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
For more information on JIRA, see: http://www.atlassian.com/software/jira