Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-26158

Active Directory authentication for Subversion plugin fails

    XMLWordPrintable

Details

    Description

      We've set up SVNKit in our Jenkins instance to use JNA to collect credentials for SVN access by setting -Dsvnkit.http.ntlm=jna in jenkins.xml. This has been working perfectly until we tried to upgrade Jenkins to 1.586, when the Jenkins JNA implementation was bumped to jna 4.10. After that, we get an "E200015: No credential to try." error.
      The last working version was Jenkins 1.585 and subversion plugin 2.4.5. If I upgrade any of them, we get the error.

      Attachments

        Issue Links

          depends on

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-28251 Subversion plugin consistent source of problems - allow native subversion client

          • Critical - Crashes, loss of data, severe memory leak.
          • Open
          duplicates

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-27084 SVN authentication fails using subversion plugin v.2.5

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Reopened
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-26473 SVN cannot authenticate using Negotiate

          • Blocker - Blocks development and/or testing work, production could not run.
          • Resolved

          Activity

            Ascending order - Click to sort in descending order
            View 9 older comments
            bennyprange Benny Prange added a comment -

            I'm having the same issue. My workaround is to use <exec> in ant and call svn directly from commandline. Eg:

             
<exec executable="svn">
  <arg line="checkout --non-interactive --trust-server-cert --username ${svn.user} --password ${svn.psw} ${svn.url} ${param.dep.dest}" />
</exec>

            Nevertheless I would love to see this bug fixed.

            bennyprange Benny Prange added a comment - I'm having the same issue. My workaround is to use <exec> in ant and call svn directly from commandline. Eg: <exec executable= "svn" > <arg line= "checkout --non-interactive --trust-server-cert --username ${svn.user} --password ${svn.psw} ${svn.url} ${param.dep.dest}" /> </exec> Nevertheless I would love to see this bug fixed.
            andreasschrell Andreas Schrell added a comment -

            I could solve a similar problem by setting the following JAVA option on jenkins startup:

            -Dsvnkit.http.methods=Basic,Digest,Negotiate,NTLM
            andreasschrell Andreas Schrell added a comment - I could solve a similar problem by setting the following JAVA option on jenkins startup: -Dsvnkit.http.methods=Basic,Digest,Negotiate,NTLM
            recena Manuel Recena Soto added a comment -

            It seems this issue is duplicate. Take a look JENKINS-27084.

            recena Manuel Recena Soto added a comment - It seems this issue is duplicate. Take a look JENKINS-27084 .
            recena Manuel Recena Soto added a comment -

            schristou, What do you think if we resolve this ticket as duplicated?

            recena Manuel Recena Soto added a comment - schristou , What do you think if we resolve this ticket as duplicated?
            schristou Steven Christou added a comment -

            This issue is a duplicate of JENKINS-27084 which was fixed in 2.5.1.

            schristou Steven Christou added a comment - This issue is a duplicate of JENKINS-27084 which was fixed in 2.5.1.

            People

              schristou Steven Christou
              ursus_b Björn Olsson
              Votes:
              7 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: