Failed to verify the server certificate: the issuer is not trusted

When starting the ANT script target, the error below appears. The error message is "Server Certificate Error." Please help fix this problem. I work in Windows XP.

C:\apache-ant-1.8.1>ant checkout Buildfile: C:\Program Files\Java\apache-ant-1.8.1\build.xml checkout: [svn] Using command line interface Svn : Checking out a working copy from a repository : co -r HEAD https://col.../trunk C:\ant-1.8.1\Test_Checkout --username 69 --password *******--non-interactive svn: PROPFIND request failed on '/svn/asia-pac-financials/trunk' svn: PROPFIND of '/sv.../trunk': Server certificate verification failed: issuer is not trusted (https://col....com) BUILD FAILED C:\apache-ant-1.8.1\build.xml:16: Can't checkout Total time: 3 seconds 
+51
svn ant
Jun 30 2018-10-10T00:
source share
9 answers

can you try to run svn checkout once manually at your https://yoururl/trunk C:\ant-1.8.1\Test_Checkout using the command line and accept the certificate.

Or as @AndrewSpear says below

Instead of manually checking the start of the svn list https://your.repository.url from the terminal (Mac) / command line (Win) to be able to constantly accept the certificate

svn will ask you to confirm. take it on an ongoing basis.

After that, this should work for subsequent requests from the ant script.

+112
Jun 30 '10 at 8:52
source share

Run the "svn help commit" to all available options. You will see that there is one parameter for accepting server certificates:

--trust-server-cert : accept unknown SSL server certificates without (but only with --non-interactive )

Add it to your svn command arguments and you won’t need to run svn manually to accept it forever.

+42
Mar 17 2018-11-11T00:
source share

I would not use:

 svn checkout 

just to authorize the server, I rather use:

 svn list https://your.repository.url 

which asks you to authenticate.

If it is necessary to obtain authorization for a user who cannot log in, run:

 sudo -u username svn list https://your.repository.url 
+9
Jan 30 '13 at 15:41
source share
 ProcessStartInfo cmd = new ProcessStartInfo("cmd.exe", @"/k svn log --trust-server-cert --non-interactive " + "\"" + servidor + "\"" + " --username alex --password alex -r " + numeroRevisao); cmd.CreateNoWindow = true; cmd.RedirectStandardOutput = true; cmd.RedirectStandardError = true; cmd.WindowStyle = ProcessWindowStyle.Hidden; cmd.UseShellExecute = false; Process reg = Process.Start(cmd); string output = ""; using (System.IO.StreamReader myOutput = reg.StandardOutput) { output += myOutput.ReadToEnd(); } using (System.IO.StreamReader myError = reg.StandardError) { output += myError.ReadToEnd(); } return output; 
+1
Nov 13
source share

from cmd: URL of the SVN list, you will be given 3 options for (r) extraction, (a) ccept, (p). enter p. This resolved issue for me

+1
May 14 '14 at 13:35
source share

If you are using svn with Jenkins on Windows Server, you must accept the https certificate using the same Windows Jenkins service user.
So, if your Jenkins service runs as "MYSERVER \ Administrator", you should use this command in front of everyone else, only once:

runas / user: MYSERVER \ Administrator "svn - userername user - password password list https: // myserver / svn / REPO "

svn asks you to accept the certificate and saves it in the right way .

After that, you can use svn in jenkins directly on the Windows command line step.

+1
May 19 '16 at 16:10
source share

Other answers do not work for me. I am trying to get the command line to work in Jenkins. All you need is the following command line arguments:

--non-interactive

--trust-server-cert

0
Aug 27 '13 at 20:35
source share

Just install the server certificate in the client’s trusted root certificates container (if it is complete, it may not work). For more information see this post on a similar question.

stack overflow

0
Jan 28 '14 at 11:38 on
source share

while the command line is running. I use Ant to capture an artifact after the build is complete. Tried the same problem ... Manually with the exception of cert didn't work (Jenkins is funny that way). Add these parameters to the svn command:

- non-interactive

- trust server-cert

0
Mar 05 '14 at 9:03
source share



All Articles