-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Package from http://pkg.jenkins-ci.org/debian/ running on Debian Wheezy/Java 7
SVN checkout or update does not work any more in version 1.473 (and 1.474) when using SSL client certificates. Apache says "access to .../svn failed, reason: SSL requirement expression not fulfilled (see SSL logfile for more details)". There's no SSL log, so no idea what it says. The certificate and pkcs12 password are valid (works if I import it into my browser) and everything works again when I go back to version 1.472. Affects both regular SVN checkouts as well as the "SCM Sync Configuration Plugin". Trying to re-authenticate (re-upload pkcs12 file and enter password) does not work.
Stack trace from a regular jub run is attached.
[JENKINS-14414] Going from 1.472 to 1.473 breaks SSL certificate authentication
Description |
Original:
SVN checkout does not work any more in version 1.473 (and 1.474). The certificate is valid (works if I import it into my browser) and everything works again when I go back to version 1.472. Affects both regular SVN checkouts as well as the "SCM Sync Configuration Plugin". Trying to re-authenticate (re-upload pkcs12 file and enter password) does not work. Stack trace from a regular jub run is attached. |
New:
SVN checkout or update does not work any more in version 1.473 (and 1.474). The certificate is valid (works if I import it into my browser) and everything works again when I go back to version 1.472. Affects both regular SVN checkouts as well as the "SCM Sync Configuration Plugin". Trying to re-authenticate (re-upload pkcs12 file and enter password) does not work. Stack trace from a regular jub run is attached. |
Description |
Original:
SVN checkout or update does not work any more in version 1.473 (and 1.474). The certificate is valid (works if I import it into my browser) and everything works again when I go back to version 1.472. Affects both regular SVN checkouts as well as the "SCM Sync Configuration Plugin". Trying to re-authenticate (re-upload pkcs12 file and enter password) does not work. Stack trace from a regular jub run is attached. |
New:
SVN checkout or update does not work any more in version 1.473 (and 1.474). The certificate and pkcs12 password are valid (works if I import it into my browser) and everything works again when I go back to version 1.472. Affects both regular SVN checkouts as well as the "SCM Sync Configuration Plugin". Trying to re-authenticate (re-upload pkcs12 file and enter password) does not work. Stack trace from a regular jub run is attached. |
Description |
Original:
SVN checkout or update does not work any more in version 1.473 (and 1.474). The certificate and pkcs12 password are valid (works if I import it into my browser) and everything works again when I go back to version 1.472. Affects both regular SVN checkouts as well as the "SCM Sync Configuration Plugin". Trying to re-authenticate (re-upload pkcs12 file and enter password) does not work. Stack trace from a regular jub run is attached. |
New:
SVN checkout or update does not work any more in version 1.473 (and 1.474) when using SSL client certificates. Apache says "access to .../svn failed, reason: SSL requirement expression not fulfilled (see SSL logfile for more details)". There's no SSL log, so no idea what it says. The certificate and pkcs12 password are valid (works if I import it into my browser) and everything works again when I go back to version 1.472. Affects both regular SVN checkouts as well as the "SCM Sync Configuration Plugin". Trying to re-authenticate (re-upload pkcs12 file and enter password) does not work. Stack trace from a regular jub run is attached. |
Summary | Original: Going from 1.472 to 1.473 breaks Certificate authentication | New: Going from 1.472 to 1.473 breaks SSL certificate authentication |
Workflow | Original: JNJira [ 145050 ] | New: JNJira + In-Review [ 176254 ] |