-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins 2.401.1, SSH Build Agents 2.877.v365f5eb_a_b_eec
I would like to connect a new agent to our Jenkins Master. It uses the paragraph character ยง in the password and the authentication fails (wrong password). Unfortunately, I am not allowed to change the password.
When I connect manually via ssh from a Linux machine, it asks for the password and accepts it. Without those special characters, the connection would also work from Jenkins. So I assume it's a bug in the plugin.
Unfortunately, it's not possible to use a SSH key instead of a password with this plugin. Would have been a viable alternative.
[JENKINS-71483] Paragraph character in password not working
Priority | Original: Blocker [ 1 ] | New: Minor [ 4 ] |
Resolution | New: Not A Defect [ 7 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Attachment | New: image-2023-06-19-17-50-11-771.png [ 60612 ] |
Attachment | New: image-2023-06-19-17-50-55-293.png [ 60613 ] |
Resolution | Original: Not A Defect [ 7 ] | |
Status | Original: Closed [ 6 ] | New: Reopened [ 4 ] |
Comment | [ Could you please use the user groups to ask questions? Jira is nor a support site, please check https://www.jenkins.io/participate/report-issue/#Howtoreportanissue-WhatinformationtoprovideforEnvironmentandDescription ] |
Status | Original: Reopened [ 4 ] | New: Open [ 1 ] |
Can you further explain your statement:
I only use SSH private keys with the Jenkins agents that I connect with SSH. I have agents running Alma Linux 8, CentOS 7, Debian 10, Debian 11, Debian 12, FreeBSD 13, Rocky Linux 9, openSUSE 15.4, Ubuntu 20.04, Ubuntu 22.04, Windows 10, and Windows 11.
I don't know how to connect a Jenkins agent using ssh with a password.
Maybe you mean that the SSH private key is protected by a passphrase and that passphrase includes the paragraph character?