[JENKINS-60215] Show ssh public keys in ssh key editing ui

[jenkins-infra-bot]

1. visit http://jenkins/credentials/store/system/domain/_/
2. click the wrench for a SSH Username with private key item

Actual results:

• Scope
• ID
• Description 
• Username
• Private Key
  • Enter directly
  • Key Concealed for Confidentiality [Replace]
• Passphrase

Expected results:

Private Key should be Key, and under Enter directly, there should be a Public Key showing the current calculated Public Key. The item currently labeled as Key should be renamed Private Key.

See also JENKINS-56940">JENKINS-56940

 

---

Originally reported by jsoref, imported from: Show ssh public keys in ssh key editing ui

• status: Open
• priority: Minor
• component(s): ssh-credentials-plugin
• resolution: Unresolved
• votes: 5
• watchers: 6
• imported: 20251215-193512

Raw content of original issue

	
visit http://jenkins/credentials/store/system/domain/_/
	
click the wrench for a SSH Username with private key item



Actual results:

	
Scope
	
ID
	
Description 
	
Username
	
Private Key
	

		
Enter directly
		
Key Concealed for Confidentiality [Replace]
	
	
	
Passphrase



Expected results:

Private Key should be Key, and under Enter directly, there should be a Public Key showing the current calculated Public Key. The item currently labeled as Key should be renamed Private Key.

See also JENKINS-56940

 

[jenkins-infra-bot]

jpyeron:

• Original comment link
• Raw content of original comment:

  conversation on mailing list says best approach is to:
  
  
  
  pipeline {
     agent any
     parameters {
        credentials credentialType: 'com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey', defaultValue: '', description: '', name: 'credential', required: true
      }
     stages {
        stage('Hello') {
           steps {
              sshagent([params.credential]) {
                  sh 'ssh-add -L'
              }
           }
        }
     }
  }
  
  
  
  

conversation on mailing list says best approach is to:

pipeline {
   agent any
   parameters {
      credentials credentialType: 'com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey', defaultValue: '', description: '', name: 'credential', required: true
    }
   stages {
      stage('Hello') {
 steps {
    sshagent([params.credential]) {
sh 'ssh-add -L'
    }
 }
      }
   }
}

[jenkins-infra-bot]

jsoref:

• Original comment link
• Raw content of original comment:

  We pay extra whenever we run jobs as we use on demand nodes exclusively.
  
  The idea that someone would have to create jobs to do this is at least user hostile.
  

We pay extra whenever we run jobs as we use on demand nodes exclusively.

The idea that someone would have to create jobs to do this is at least user hostile.

[jenkins-infra-bot]

jpyeron:

• Original comment link
• Raw content of original comment:

  This is why I am trying to patch the plugin right now.
  
  In our case, those who need the public key (systems admins) do not have the ability to create jobs either.
  

This is why I am trying to patch the plugin right now.

In our case, those who need the public key (systems admins) do not have the ability to create jobs either.