[ 
https://issues.jenkins-ci.org/browse/JENKINS-3912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162297#comment-162297
 ] 

Dustin Parker commented on JENKINS-3912:
----------------------------------------

Hate to "me too", but we're running up against this problem, too on Jenkins 
1.462, SVN plugin 1.39. Specifying username/password gives an NPE, specifying 
certificate gives 401 just like the commenter above. I'd love for this bug to 
be fixed, but is there any way I can work around this problem for now? Some 
combination of environment variables and editing configuration files that'll 
get Jenkins+SVNKit to use the credentials and certificate file?
                
> support for both client cert & username/password auth to SVN
> ------------------------------------------------------------
>
>                 Key: JENKINS-3912
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-3912
>             Project: Jenkins
>          Issue Type: Improvement
>          Components: subversion
>    Affects Versions: current
>         Environment: Platform: All, OS: Windows XP
>            Reporter: jrissone
>            Priority: Critical
>
> I have a need to use two authentication methods (HTTPS client certs and 
> username/password) for access to the SVN server. Aside from the additional 
> security provided by having username/pw on the SVN repo, it is useful to 
> control authorization permissions by user with a username/pw for each 
> acccount 
> accessing the repo. Since Hudson uses radio buttons to select the SVN 
> authentication options, it does not appear to be possible to use both and 
> have 
> it connect to the SVN repository without removing one of the authentication 
> measures currently in place.
> If there is not a plugin that addresses this case, it would be helpful if 
> Hudson supported multiple authentication options (or at least those two).

--
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

        

Reply via email to