[
https://issues.jenkins-ci.org/browse/JENKINS-13763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Borm updated JENKINS-13763:
---------------------------------
Summary: subversion https-client authentication doesn't work with
correct parameters (was: subversion authentication doesn't work on correct
certificate parameters)
Attachment: emptycertificate.png
subversionException.txt
Description:
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.
was:
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.
> subversion https-client authentication doesn't work with correct parameters
> ---------------------------------------------------------------------------
>
> Key: JENKINS-13763
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13763
> Project: Jenkins
> Issue Type: Bug
> Components: subversion
> Affects Versions: current
> Environment: Windows Server 2003, Java 1.6.0.31, Jenkins 1.463,
> Subversion Plugin 1.39
> Reporter: Marco Borm
> Attachments: emptycertificate.png, emptycertificate.png,
> subversionException.txt, subversionException.txt
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
