Uploaded image for project: 'Maven Wagon'
  1. Maven Wagon
  2. WAGON-372

SSL client-side certificates stopped working in maven 3.0.4

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.2
    • 2.4
    • wagon-http
    • None
    • Fedora, Ubuntu

    Description

      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.

      Attachments

        Issue Links

        is depended upon by

        Bug - A problem which impairs or prevents the functions of the product. WAGON-383 Regression for SSLv3

        • Critical - Crashes, loss of data, severe memory leak.
        • Closed
        is related to

        Improvement - An improvement or enhancement to an existing feature or task. MNG-5175 replace wagon http lightweight with wagon http 2.1

        • Major - Major loss of function.
        • Closed

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            olamy Olivier Lamy
            ivonnyssen Igor von Nyssen
            Votes:
            3 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment