• Type: Bug
• Resolution: Not A Defect
• Priority: Major
• Component/s: ssh-credentials-plugin
• Labels:

  • credentials
  • jenkins
  • plugin
  • ssh
• Environment:

  Jenkins ver. 1.625.3.1 (CloudBees Jenkins Enterprise 15.11)
  Java 8
  RHEL 7
  SSH Credentials Plugin 1.11/1.10

[JENKINS-32876] ssh shell command fails with "Too many authentication failures for ..." on ssh credentials plugin 1.11

Kevin Rancka created issue - 2016-02-10 11:45

Kevin Rancka made changes - 2016-02-10 11:46

Environment

Original: Jenkins ver. 1.625.3.1 (CloudBees Jenkins Enterprise 15.11) Java 8 RHEL 7

New: Jenkins ver. 1.625.3.1 (CloudBees Jenkins Enterprise 15.11) Java 8 RHEL 7 SSH Credentials Plugin 1.11/1.10

Kevin Rancka made changes - 2016-02-10 11:46

Description

Original: When executing a shell command like ssh to connect to a server, the connection fails with: 09:36:59 Authorized uses only. All activity may be monitored and reported. 09:36:59 Permission denied, please try again. 09:36:59 Permission denied, please try again. 09:36:59 Received disconnect from xx.xx.xx.xx: 2: Too many authentication failures for xxx 09:36:59 lost connection 09:36:59 Build step 'Execute shell' marked build as failure 09:36:59 [ssh-agent] Stopped. After downgrading to version 1.10 everything works fine.

New:  When executing a shell command like ssh to connect to a server (with ssh credentials plugin v1.11), the connection fails with: 09:36:59 Authorized uses only. All activity may be monitored and reported. 09:36:59 Permission denied, please try again. 09:36:59 Permission denied, please try again. 09:36:59 Received disconnect from xx.xx.xx.xx: 2: Too many authentication failures for xxx 09:36:59 lost connection 09:36:59 Build step 'Execute shell' marked build as failure 09:36:59 [ssh-agent] Stopped. After downgrading to version 1.10 everything works fine.

Collapse comment: Stephen Connolly added a comment - 2016-06-17 11:17

Stephen Connolly added a comment - 2016-06-17 11:17

Most likely you have multiple keys in your credentials and the ssh server is not configured to allow sufficient attempts in order to let the correct key work.

Expand comment: Stephen Connolly added a comment - 2016-06-17 11:17

Stephen Connolly added a comment - 2016-06-17 11:17 Most likely you have multiple keys in your credentials and the ssh server is not configured to allow sufficient attempts in order to let the correct key work.

Stephen Connolly made changes - 2016-06-17 11:17

Resolution		New: Not A Defect [ 7 ]
Status	Original: Open [ 1 ]	New: Closed [ 6 ]

R. Tyler Croy made changes - 2016-07-26 00:01

Workflow

Original: JNJira [ 168573 ]

New: JNJira + In-Review [ 209699 ]