[
https://jira.codehaus.org/browse/WAGON-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski updated WAGON-372:
------------------------------------
Attachment: maven-httpwagen-httpclient-ssl-setup-refactoring.patch
Let us try to tackle the problem in several incremental steps. Could you please
see if all test cases pass for you locally with this patch only? The patch only
refactors the SSL initialization code sowewhat without (intentionally) changing
its behavior.
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,
> 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:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
