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

Subversion Authentication: Field for Private key does not allow file path on server to specified

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • subversion-plugin
    • None

      I am using the "svn+ssh" protocol to access my Subversion repository. The SSH Private keys are stored on a Cent-OS 5.3 server where I am running Hudson.

      In setting up the Hudson Subversion Authentication I attempt to enter the path to the SSH Private Key. I am presented with a File Explorer window that requires me to specify a path on my Windows XP machine where I am running the Web Browser.

      This will not do. The SSH Private key is located on the Cent-OS 5.3 machine where the Hudson process is running and NOT on my Windows machine where I am running the browser.

          [JENKINS-6511] Subversion Authentication: Field for Private key does not allow file path on server to specified

          acarr0 added a comment -

          As a work around I had to scp the SSH Private key to my Windows XP desktop machine so that I could the upload it back into Hudson.

          acarr0 added a comment - As a work around I had to scp the SSH Private key to my Windows XP desktop machine so that I could the upload it back into Hudson.

          evernat added a comment -

          Being able to define a server path, instead of having to upload the SSH private key, seems not a critical bug to me.
          First because it is "quite simple" to get the key to be uploaded, as you have done.
          So changing the issue to be a minor improvement, and thanks for the feedback anyway.

          evernat added a comment - Being able to define a server path, instead of having to upload the SSH private key, seems not a critical bug to me. First because it is "quite simple" to get the key to be uploaded, as you have done. So changing the issue to be a minor improvement, and thanks for the feedback anyway.

          Daniel Robert added a comment - - edited

          While it may be 'quite simple' to upload the key, many user accounts/keys are centrally managed by something like Chef or Puppet. While the keypairs may be periodically updated as needed by security audit or breakin or just general shifting around of accounts, these tools are not equipment to periodically re-upload the key to Jenkins.

          Daniel Robert added a comment - - edited While it may be 'quite simple' to upload the key, many user accounts/keys are centrally managed by something like Chef or Puppet. While the keypairs may be periodically updated as needed by security audit or breakin or just general shifting around of accounts, these tools are not equipment to periodically re-upload the key to Jenkins.

            Unassigned Unassigned
            acarr0 acarr0
            Votes:
            2 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: