Details
-
Bug
-
Status: Reopened (View Workflow)
-
Minor
-
Resolution: Unresolved
-
None
-
Windows Server 2008 R2,
Jenkins 1.599
Description
We're using username and password over HTTP as authentication to the svn server and the Jenkins service is running as the same user.
Recently we upgraded the subversion plugin to v2.5 from v2.4.5 and this caused svn authentication to fail with the following error:
svn: E200015: authentication cancelled
Diving deeper into the cause of this revealed that Jenkins no longer tries to login to the svn server using HTTP clear text authorization (don't know the real name for this) but now tries to use NTLMSSP. Jenkins seems to use the correct username using NTLMSSP but the authentication fails.
Attachments
Issue Links
- is duplicated by
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- is related to
-
-
- Closed
-
Activity
Thank you! That worked but I don't understand why it worked? Didn't I just specify the same credentials again without the specific directory?
Doesn't it try to use the same credentials when resolving an External?
And previous versions didn't have this problem.
Jens Bjerre
added a comment - - edited Thank you! That worked but I don't understand why it worked? Didn't I just specify the same credentials again without the specific directory?
Doesn't it try to use the same credentials when resolving an External?
And previous versions didn't have this problem. See JENKINS-21785. It's supposedly a security enhancement on forcing externals to be explicitly defined with their credentials. Not sure why only the changelog calculation is affected and not the actual checkout... It definitely does not use the same credentials as the Repository URL anymore when accessing externals.
John Schroeder
added a comment - I'm getting the:
org.tmatesoft.svn.core.SVNCancelException: svn: E200015: authentication cancelled
When trying to connect to an Assembla SVN repository via SSH. I am able to connect via HTTP with a username and password but not through SSH. I've tried all of the workarounds listed here with no success.
Assembla requires that an environment variable called REPO_NAME be set and forwarded for svn+ssh. The environment variable is set and the SendEnv is configured in ~/.ssh/config:
Host subversion.assembla.com
SendEnv REPO_NAME
It works via the command line as the Jenkins user. Will this be send through the subversion plugin in Jenkins?
John Schroeder
added a comment - I'm getting the:
org.tmatesoft.svn.core.SVNCancelException: svn: E200015: authentication cancelled
When trying to connect to an Assembla SVN repository via SSH. I am able to connect via HTTP with a username and password but not through SSH. I've tried all of the workarounds listed here with no success.
Assembla requires that an environment variable called REPO_NAME be set and forwarded for svn+ssh. The environment variable is set and the SendEnv is configured in ~/.ssh/config:
Host subversion.assembla.com
SendEnv REPO_NAME
It works via the command line as the Jenkins user. Will this be send through the subversion plugin in Jenkins? For what it's worth, I was getting "svn: E200015: authentication cancelled" because my svn repo was using a self signed cert. I had to add that cert to java's cacerts keystore, using portecle on Windows, and then it worked fine.
Brenden Keyes
added a comment - - edited For what it's worth, I was getting "svn: E200015: authentication cancelled" because my svn repo was using a self signed cert. I had to add that cert to java's cacerts keystore, using portecle on Windows, and then it worked fine. 
Hi Jens,
Try adding "additional credentials" in your job with the realm defined as svn+ssh://svn.example.com with credentials that fit with that server/repo.
Thanks,
Channy