[
https://issues.jenkins-ci.org/browse/JENKINS-13763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162732#comment-162732
]
Marco Borm commented on JENKINS-13763:
--------------------------------------
Ok, the mistake was a missing password character. So the workaround works also
under linux, but: The error message was wrong again. "No credential to try" ->
"found credentials wrong"
> 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
