-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Windows Server 2003, Java 1.6.0.31, Jenkins 1.463, Subversion Plugin 1.39
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.
- is related to
-
JENKINS-13763 subversion https-client authentication doesn't work with correct parameters
-
- Closed
-