Marco Borm created JENKINS-13763:
------------------------------------
Summary: subversion authentication doesn't work on correct
certificate 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, subversionException.txt
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.
--
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
