Failing authentification for svn://

[mremer...@aim.com]

Hi,

we have changed our SVN connection from https to svn:// .

If I change the SVN Url in a jenkins job now from https to the svn:// connection it complains

svn: SASL(-13): authentication failure: Password verification failed

I tried to authenticate myself in Jenkins via the "Subversion authentification", but entering the correct user with the correct password it prints again

FAILED: svn: SASL(-13): authentication failure: Password verification failed

org.tmatesoft.svn.core.SVNAuthenticationException: svn: SASL(-13): authentication failure: Password verification failed

	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:62)

	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)

	at org.tmatesoft.svn.core.internal.io.svn.sasl.SVNSaslAuthenticator.authenticate(SVNSaslAuthenticator.java:142)

	at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.authenticate(SVNConnection.java:173)

	at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.authenticate(SVNRepositoryImpl.java:1265)

	at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.openConnection(SVNRepositoryImpl.java:1243)

	at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.testConnection(SVNRepositoryImpl.java:95)

	at hudson.scm.SubversionSCM$DescriptorImpl.postCredential(SubversionSCM.java:1754)

	at hudson.scm.SubversionSCM$DescriptorImpl.doPostCredential(SubversionSCM.java:1699)

	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

	at java.lang.reflect.Method.invoke(Method.java:597)

	at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:282)

	at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:149)

	at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:88)

	at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:102)

	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)

	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:562)

	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:640)

	at org.kohsuke.stapler.MetaClass$7.doDispatch(MetaClass.java:242)

	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)

	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:562)

	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:640)

	at org.kohsuke.stapler.MetaClass$7.doDispatch(MetaClass.java:242)

	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)

	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:562)

	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:640)

	at org.kohsuke.stapler.MetaClass$7.doDispatch(MetaClass.java:242)

	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)

	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:562)

	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:640)

	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:478)



	at org.kohsuke.stapler.Stapler.service(Stapler.java:160)

If I start a checkout / commit or whatever from the console of the server Jenkins is running on, everything works fine.... so user name and password a a) correct and b) are stored on the server as consecutive calls dont ask for verification

can anyone tell me what is going wrong and why Jenkins does not recognize it ?

Thanks

[mremer...@aim.com]

oh i missed:

I am using Jenkins 1.401

[Ian C. Roberts]

Hi,

Im using hudson at the moment and havent upgraded to using jenkins - but its probably the same.

In my ~/.hudson folder i have an xml file for svn scm, this is where hudson/jenkins stores the credentials. It might be worth you having a look at this file, or move it out of the way and try to setup the scm again.
Can't help further because i use public key authentication with my svn+ssh connection.

Regards,
Ian

[Matthew...@diamond.ac.uk]

Be aware there is a bug (https://issues.jenkins-ci.org/browse/JENKINS-8059) where Jenkins keeps trashing the SVN credentials. This affects users who use the svn command line client in addition to having Jenkins check out their source. The bug is marked as fixed in Hudson (I haven't verified that, we are using Jenkins).

> -----Original Message-----
> From: jenkins...@googlegroups.com [mailto:jenkinsci-
> us...@googlegroups.com] On Behalf Of Ian C. Roberts
> Sent: 04 May 2011 10:59
> To: jenkins...@googlegroups.com
> Subject: Re: Failing authentification for svn://
>