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

git plugin does not support username/password over ssh

    Details

    • Similar Issues:

      Description

      We are trying to connect to a Git repository via SSH (not Github) using username/password (we're not using keys) and we're getting the following error:

      Failed to connect to repository : Command "git ls-remote -h ssh://account@repository/path/toApplication HEAD" returned status code 128:
      stdout:
      stderr: Permission denied, please try again.
      Permission denied, please try again.
      Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).
      fatal: Could not read from remote repository.

      Please make sure you have the correct access rights
      and the repository exists.
      ------------------

      If we use the anonymous access or change the access type from SSH to HTTPS, it works fine, but we should be able to use the SSH with user/password without having to add the public/private keys.

      Jenkins ver. 1.532.1
      Git Client Plugin 1.6.4
      Git Plugin 2.0.4
      •How are you running Jenkins?
      We are running Jenkins as a service in RHEL
      •Have you specified additional parameters for the Java VM (Heapspace etc.)?
      No
      •Did you just install the deb or rpm?
      We used the RPM jenkins-1.532.1-1.1.noarch.rpm
      •With which Java VM (Oracle, IBM etc.)?
      java version "1.7.0_45"
      Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
      Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)
      •On which operating system? 32- or 64-bit?
      Linux version 2.6.32-358.23.2.el6.x86_64 (mockbuild@ca-build44.us.oracle.com) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-3) (GCC) )

        Attachments

          Issue Links

            Activity

            Show
            jimklo Jim Klo added a comment - I'm not sure if this is related, however it sound's very similar: https://issues.jenkins-ci.org/browse/JENKINS-24368?focusedCommentId=246537&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-246537
            Hide
            markewaite Mark Waite added a comment - - edited

            Jim Klo I don't think they are related, since I believe they use different paths through the code for ssh based authentication and https based authentication. JENKINS-24368 is specific to https. (and seems to be specific to bitbucket) I can connect to a bitbucket repo with ssh, just not with https in certain configurations.

            Show
            markewaite Mark Waite added a comment - - edited Jim Klo I don't think they are related, since I believe they use different paths through the code for ssh based authentication and https based authentication. JENKINS-24368 is specific to https. (and seems to be specific to bitbucket) I can connect to a bitbucket repo with ssh, just not with https in certain configurations.
            Hide
            jaswo Jason Worick added a comment -

            I do not want to sound pushy, but this issue was created since May 2014 and its now March 2016. Can someone that is responsible for resolving this bug give an indication as to when it will be resolved? Thanks!

            Show
            jaswo Jason Worick added a comment - I do not want to sound pushy, but this issue was created since May 2014 and its now March 2016. Can someone that is responsible for resolving this bug give an indication as to when it will be resolved? Thanks!
            Hide
            markewaite Mark Waite added a comment - - edited

            Jason Worick I'm probably the only one that is close to "responsible for resolving this bug", so I'll give you my estimate. I don't know that it will be resolved any time within the next few years. A private key works quite well with ssh protocol, so I perceive there is a relatively simple work around to allow access to ssh protected git repositories.

            I'm currently focused on other areas, like adding authenticated submodule access, and like processing the ~50 pull requests pending on the git plugin, and the ~5 pull requests pending on the git client plugin.

            My first goal is to not regress functionality for the existing 70000+ installations of the plugin. I'd love to have additional help from others evaluating the pull requests, and submitting proposed improvements (fixes or features) with tests to support those additions. I'd also love to have additional automated tests for the existing features.

            Show
            markewaite Mark Waite added a comment - - edited Jason Worick I'm probably the only one that is close to "responsible for resolving this bug", so I'll give you my estimate. I don't know that it will be resolved any time within the next few years. A private key works quite well with ssh protocol, so I perceive there is a relatively simple work around to allow access to ssh protected git repositories. I'm currently focused on other areas, like adding authenticated submodule access, and like processing the ~50 pull requests pending on the git plugin, and the ~5 pull requests pending on the git client plugin. My first goal is to not regress functionality for the existing 70000+ installations of the plugin. I'd love to have additional help from others evaluating the pull requests, and submitting proposed improvements (fixes or features) with tests to support those additions. I'd also love to have additional automated tests for the existing features.
            Hide
            battika Attila Strba added a comment -

            I have just encountered the same issue but happens only on Windows Slave if using SSH username thus credentialsID with the git plugin. On Linux Slave works, and as said it also works with ssh keys. So my workaround was to go with the ssh keys.

            Show
            battika Attila Strba added a comment - I have just encountered the same issue but happens only on Windows Slave if using SSH username thus credentialsID with the git plugin. On Linux Slave works, and as said it also works with ssh keys. So my workaround was to go with the ssh keys.

              People

              • Assignee:
                agalaviz Aleyda Galaviz
                Reporter:
                agalaviz Aleyda Galaviz
              • Votes:
                4 Vote for this issue
                Watchers:
                13 Start watching this issue

                Dates

                • Created:
                  Updated: