Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-13763

subversion https-client authentication doesn't work with correct parameters

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • subversion-plugin
    • None
    • Windows Server 2003, Java 1.6.0.31, Jenkins 1.463, Subversion Plugin 1.39

      The subversion authentication module currently doesn't work, even with correct parameters. The behavior is identical to the already created bug due the not validating input parameters. The exception gives no hint what the problem / reason is.

      The authentication works perfectly if the same certificate (p12) file and the same password is configured manually within the subversion "Application Data\Subversion\servers" file.

          [JENKINS-13763] subversion https-client authentication doesn't work with correct parameters

          Marco Borm created issue -
          Marco Borm made changes -
          Attachment New: emptycertificate.png [ 21821 ]
          Attachment New: subversionException.txt [ 21822 ]
          Description Original: The subversion authentication module accepts any file as certificate and anything as password. A failure always results in the same not helpful exception "SSL handshake failed: 'Received fatal alert: handshake_failure'" after the subversion client send a empty client certificate send to the server on the TLS connection. I am not sure if is allowed to send a empty client certificate message to the server.

          Due the complexity of the software chain and configuration parameters used for HTTPS authentication, it is very annoying to find the real problem if no component returns a usable error message.

          The expected behavior is to validate the input parameters and do not try to establish a connection with obvious invalid parameters.
          New: The subversion authentication module currently doesn't work, even with correct parameters. The behavior is identical to the already created bug due the not validating input parameters. The exception gives no hint what the problem / reason is.

          The authentication works perfectly if the same certificate (p12) file and the same password is configured manually within the subversion "Application Data\Subversion\servers" file.
          Summary Original: subversion authentication doesn't work on correct certificate parameters New: subversion https-client authentication doesn't work with correct parameters
          Marco Borm made changes -
          Link New: This issue is related to JENKINS-13762 [ JENKINS-13762 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 144230 ] New: JNJira + In-Review [ 176106 ]
          James Dumay made changes -
          Resolution New: Cannot Reproduce [ 5 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            Unassigned Unassigned
            mborm Marco Borm
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: