Could not authenticate to server: rejected Basic challenge

[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building MYProject 1.2-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] --- properties-maven-plugin:1.0-alpha-2:read-project-properties (read-properties-file) @ MI-Lsvn ---
[INFO]
[INFO] --- maven-scm-plugin:1.8.1:checkout (update-source) @ MI-Lsvn ---
[INFO] Removing C:\Users\80929\.hudson\jobs\TEST_LSVN\workspace\buildme
[INFO] Executing: cmd.exe /X /C "svn --username 80929 --password ***** --no-auth-cache --non-interactive checkout -r HEAD http://........../CodeBase/ C:\Users\80929\.hudson\jobs\TEST_LSVN\workspace\buildme"
[INFO] Working directory: C:\Users\i80929\.hudson\jobs\TEST_LSVN\workspace
[ERROR] Provider message:
[ERROR] The svn command failed.
[ERROR] Command output:
[ERROR] svn: E170001: PROPFIND of '/svn/lsvn/!svn/vcc/default': authorization failed: Could not authenticate to server: rejected Basic challenge (http://lsvn)

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------

I had encountered above message while creating build from Jenkins featuring maven.

In maven i had used maven-scm-plugin plugins to checkout/update codebase. I came to know that although i had set correct username and password in plugins configuration, Jenkins User credential overwrites scm authentication provided on plugins configuration or Jenkins is not able to read credential define on maven-scm-plugins. Because if i put pom.xml file from outside .jenkins job directory and hit maven goal mvn scm:checkout or scm:update, it will succeed to do assign goal

Here below is scm plugins implementation in my pom.xml file

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-scm-plugin</artifactId>
<version>1.8.1</version>
<configuration>
....
<username>...</username>
<password>${svn.password}</password>
......
</configuration>
<executions>
<execution>
<id>update-source</id>
<phase>prepare-package</phase>
<goals>
<goal>checkout</goal>
<goal>update</goal>
</goals>
</execution>
</executions>
</plugin>

Any suggestion there to solve this problem?

Another solution i got is run scm piror to build by defining repo url and credential on jenkins interface but my aim is to get it done from maven(pom.xml).

Help me!!!

As far as I know your solution is the only solution - you need to run at least one Subversion command from the Jenkins builds slave and supply the Subversion credentials when asked before you can perform builds through Jenkins on that build slave.

One thought: you could try coping the Subversion credential store from a PC where you have already logged into the Subversion server to the Jenkins build slave.